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

Annotations already declare readOnlyHint=true, so the description correctly avoids repeating that. It adds context about the underlying 'V3 graph brain (Supabase PostgreSQL)' and that every scored prompt contributes, which is useful but doesn't cover potential performance or data freshness characteristics.

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 three sentences, front-loaded with the main question, and no extraneous text. However, it would be improved by integrating parameter details, which would not add significant length.

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?

While the tool has an output schema (so return values are not needed), the description fails to cover the input parameters and usage context, making the tool incomplete for an agent to select and invoke without external knowledge. The description is adequate for a human who knows the parameters but not for an autonomous agent.

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%, and the description provides no explanation of the two parameters (generator, grade). The word 'high-grade' hints at the grade parameter, but the description does not explicitly define how to use grade or confirm that generator is required. This is a critical gap for correct invocation.

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 it's a community graph that returns top patterns by type, enhancement unlocks, and cross-model universal patterns, distinguishing it from siblings like score_prompt or enhance_prompt. However, it uses a rhetorical phrase rather than a direct imperative verb like 'Get' or 'List', slightly reducing clarity.

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 explicit guidance on when to use this tool versus alternatives. The description implies it's for discovering high-grade patterns for a generator, but never discusses when-not-to-use or mentions sibling tools like analyze_winning_formula.

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