listPets

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

No annotations are provided, so the description carries full burden. It states 'List all pets' but does not disclose read-only behavior, whether pagination occurs, rate limits, or any side effects. Minimal behavioral insight for a simple list operation.

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?

The description is extremely concise (one sentence), front-loaded with the verb 'list'. However, it may be under-specified for the agent to use effectively, balancing conciseness with completeness.

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?

Given no output schema and no annotations, the description should provide more context (e.g., result structure, pagination, defaults). It is insufficient for the agent to understand the full behavior, especially with a single optional parameter.

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% for the only parameter 'limit', but its description is generic ('query parameter'). The tool description adds no additional meaning beyond the schema, fitting the baseline of 3 for high coverage.

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?

The description 'List all pets' clearly states it retrieves a list of pets. It distinguishes from sibling tools 'createPet' and 'getPet' implicitly (creates vs. lists vs. individual get), but does not explicitly differentiate scope or filtering.

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?

No guidance on when to use this tool vs. alternatives, no mention of pagination, filtering, or limitations. The description does not help the agent decide between listPets and getPet.

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