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

No annotations exist, so the description bears full responsibility for behavioral disclosure. It mentions returning 'full canonical record' and 'version history' but does not address destructive potential, authentication needs, rate limits, or error handling (e.g., what happens if service_id is invalid).

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, consisting of one sentence that covers the key aspects. It is front-loaded with the primary purpose. However, it could be slightly more structured (e.g., listing what 'full canonical record' includes).

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 low complexity (1 required parameter, output schema exists), the description is minimally adequate. It vaguely describes the output without specifics; while the output schema can fill details, the description lacks context on version history and what 'full canonical record' entails. Not severely lacking but has room for improvement.

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 0% for the single parameter service_id, and the description does not elaborate on its meaning or source (e.g., from search results). The description fails to compensate for the missing schema documentation.

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 returns the full canonical record and version history for one service business. It distinguishes from sibling get_*_details tools by specifying the 'service business' category, but could be more explicit about what constitutes the 'canonical record'.

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 is provided on when to use this tool versus alternative get_*_details tools for other categories (e.g., apparel, community). There is no mention of prerequisites or context for choosing this tool.

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