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

With no annotations provided, the description carries the full burden. It discloses coverage ('Global') and per-endpoint pricing, which adds useful context. However, it does not mention authentication, rate limits, response formats, or whether operations are read-only. The 'AI-synthesized' tag hints at behavior but lacks detail. The truncation also undermines transparency.

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 structured with a summary, coverage, and a bulleted endpoint list, making it easy to scan. However, it is somewhat lengthy, and the truncated opening sentence ('and franchise br') is a clear flaw that interrupts readability. It earns credit for front-loading the main purpose but loses points for the incomplete thought.

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 complexity (15 parameters, no output schema, no annotations), the description is incomplete. It does not specify which parameters are required or optional for each endpoint, nor does it describe the response structure. An agent would struggle to know exactly how to invoke actions like 'discover' or 'compare' with the right parameters. The endpoint list is helpful but insufficient for correct invocation.

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%, but most parameter descriptions are tautological (e.g., 'location' is described as 'location'). The description lists endpoints, which indirectly suggests which parameters might be relevant (e.g., 'concepts' for comparison), but does not directly explain parameters. It adds some value beyond the schema but does not compensate for the unhelpful schema descriptions.

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 this is a 'Global franchise intelligence API' and lists specific endpoints with one-line explanations (e.g., 'FDD analysis', 'franchise opportunity discovery'). This distinguishes it from sibling tools by focusing on franchise-related data. However, the opening sentence is truncated ('and franchise br'), preventing a perfect score.

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 implies usage for franchise intelligence through its title and endpoint list, but it does not explicitly state when to use this tool vs alternatives. There is no mention of exclusions or specific prerequisites. The endpoint list provides context for different use cases, but no direct guidance on when to select this tool over sibling 'pulse' tools.

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