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

Annotations already declare `readOnlyHint: true`, confirming no side effects. The description adds context about what the tool returns (score, missing patterns, ROI patterns), which goes beyond annotations. However, it does not disclose other behavioral traits like auth requirements, rate limits, or the nature of the comparison. With annotations covering the safety profile, the description adds moderate value.

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 two sentences long (78 words total), front-loads the core purpose in the first sentence, and wastes no words. Every sentence adds value—purpose then return values. This is an exemplary model of conciseness.

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?

The tool has two required string parameters, is read-only, and has an output schema (not shown). The description covers the return values (score, missing patterns, ROI patterns) adequately. It does not elaborate on what 'community top scorers' means or how the comparison works, but given the output schema likely provides that information, the description is sufficiently complete 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 0%, so the description must compensate. It does so by mentioning 'your prompt' and 'this generator', implying that `prompt` is the user's prompt and `generator` is the generator name. This adds essential meaning beyond the schema, but lacks further detail like format or constraints. Given the baseline of 4 for zero params, this is adequate.

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: 'Compare your prompt against community top scorers for this generator.' It specifies the action (compare), the resource (prompt vs community top scorers), and mentions the return values (score, missing patterns, ROI patterns). This distinguishes it from sibling tools like 'score_prompt' which likely only returns a score, or 'enhance_prompt' which modifies the prompt.

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 provides clear context on when to use the tool: when you want to compare your prompt to community benchmarks for a specific generator. However, it does not explicitly exclude scenarios or name alternatives, which would warrant a 5. The implicit guidance is sufficient for an agent to infer usage, but lacks explicit prohibition or sibling differentiation.

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