list_favorites

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the agent already knows this is a safe read operation that may return external data. The description adds no further behavioral details such as pagination, sorting, or rate limits. With annotations covering safety and openness, the description is minimally adequate but adds little.

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?

A single, front-loaded sentence with no redundant words. Efficiently states the action and result.

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?

For a simple no-param read tool, the description is functionally complete. However, given the many sibling tools that also list vendors or favorites, it lacks the disambiguation that would make it fully useful. The absence of an output schema is acceptable, but the description could clarify the return shape or scope.

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?

The tool takes no parameters; the schema is empty and 100% covered. The description correctly implies a parameterless retrieval, and no additional parameter semantics are needed. Baseline for zero params is 4.

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?

Clear verb 'List' and resource 'favorited/saved vendors', specifying the collection being returned. However, it does not distinguish itself from the sibling 'list_favorite_card_suites' or from 'list_vendors', leaving ambiguity about what constitutes a 'favorite' versus a general vendor list.

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 versus 'list_vendors' or 'list_favorite_card_suites'. The description provides no context about prerequisites or scenarios that would select this tool over alternatives.

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