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

The description goes well beyond the annotations. It discloses that the tool returns metadata only (no persona text or skill instructions), the exact return format with an example, error behavior (never protocol error, returns error object), and that it's read-only and idempotent (aligning with annotations). No contradictions with annotations.

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 well-structured and front-loaded with the core purpose. Each sentence provides essential information: what it lists, that it's free, no arguments, example output, usage guidance, behavioral limits, alternatives, and error handling. Nothing is redundant or extraneous.

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's simplicity (0 parameters, clear output schema, comprehensive annotations), the description is complete. It covers purpose, usage, return format, error behavior, and alternatives. The output schema exists, so the description doesn't need to explain return values beyond what it provides.

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 input schema has 0 parameters with 100% coverage, so the baseline is 3. The description adds value by stating 'Takes no arguments' and showing the typical input {} and output format, which helps the agent understand the exact behavior. This is clear and complete.

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 clearly states the tool lists every product in the Business Suite line with included skills. It distinguishes itself from siblings by explicitly naming get_free_skill, get_full_product, and get_full_skill as alternatives for different purposes. The verb 'list' and resource 'products' are specific and unambiguous.

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 explicitly says when to use this tool ('when the caller wants to see what this server covers'), and when not to use it ('not for keyword search across the whole 138-product catalog, which the catalog server's search_catalog does, and not for instructions the caller can act on (get_free_skill)'). It names alternative tools and provides clear context.

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