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

The description states it 'uses live data and structured AI analysis across 5 dimensions' and is 'Not hallucinated.' It also outlines return values (dimension scores, winner, etc.). With no annotations provided, the description provides reasonable behavioral context, though it omits details like idempotency or permission requirements.

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 concise: two sentences defining the core function, then examples, then return summary, then trigger phrases. Every sentence serves a purpose. Information is front-loaded and well-organized.

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 relative simplicity (3 params, no output schema), the description is quite complete: it covers inputs, examples, output format, and usage triggers. However, it lacks details on error handling or limitations (e.g., unsupported comparison types), which would be needed for perfect completeness.

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 coverage is 100%, so baseline is 3. The description adds value by giving examples for each parameter and explaining the 'context' parameter as 'your specific use case or constraint.' This goes beyond the schema's simple 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 the tool's purpose: 'Real-time head-to-head comparison of any two things — with a structured verdict and winner.' It provides specific examples (AI models, frameworks, tools, etc.) that distinguish it from sibling tools, which are various agents and utilities, none of which focus on comparison.

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 lists trigger phrases: 'Use when the user says: 'compare', 'vs', 'which is better', 'should I use X or Y', 'what's the difference between'.' It also provides examples of applicable domains. However, it does not mention when not to use the tool or suggest alternatives, missing the 'when-not' aspect for a perfect score.

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