List Products

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds only that products are reusable items for invoices/quotes, which provides context but no additional behavioral traits like rate limits, authentication needs, or side effects beyond what annotations cover.

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 bilingual (English and Spanish), adding length but is front-loaded with English. It is clear and efficient, though the bilingual repetition could be streamlined. Each sentence serves a purpose.

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 the tool has 6 parameters, optional pagination, and an output schema, the description adequately covers what the tool does and what products are. It does not explain return format, but the output schema handles that. Sufficient for the complexity level.

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% (all 6 parameters well-documented). The description only mentions 'optional pagination', which adds minimal meaning beyond the schema. Baseline score of 3 applies when schema covers parameters adequately.

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?

Description clearly states 'List all products/services' with specific verb and resource, and distinguishes from sibling tools like create_product, get_product, delete_product. Provides context about products being reusable items for invoices and quotes.

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?

The description mentions optional pagination, hinting at usage for large result sets, but does not explicitly state when to use this tool versus alternatives like search_invoices or other listing tools. No exclusions or when-not-to-use guidance provided.

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