List App Configurations

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses paginated JSON array output and pagination metadata. Annotations already provide readOnlyHint, destructiveHint, etc. No contradictions. Adds value with pagination details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, each with a distinct purpose: purpose, use cases, output/pagination, required parameter and API reference. No unnecessary words. Well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core aspects: resource type, output format, pagination, required parameter. Does not detail all filter parameters but schema covers them. Sufficient for a list tool without output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. Description adds context around pagination ('Use page and per_page to control pagination') and emphasizes the required company_id, which is already in schema but reinforced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Returns a list of app configurations on a given company or project' with a specific verb and resource. Distinguishes itself by mentioning 'App Marketplace records' and enumeration use case, differentiating from sibling list tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit use cases: 'when you need a paginated overview, to find IDs, or to filter by query parameters.' Does not mention when not to use or alternatives, but the context is clear enough for effective tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.