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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context: results are ordered by composite score, all sub-scores are visible, and the default is evidence-ranked only. This goes beyond annotations without contradicting them, offering valuable insight into how the tool behaves.

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 short sentences, front-loaded with the primary function and a key detail about the output. It is concise, clear, and contains no filler or redundant repetition of schema data.

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 a clear output schema and robust annotations, so the description does not need to explain return values or safety. The description adequately covers purpose, ordering, and default filtering. The missing usage guidelines are a small gap, but for a simple ranking tool the description is otherwise complete.

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?

The input schema has 100% description coverage for all three parameters, including enums and defaults. The description adds a little extra meaning by mentioning composite score and sub-scores, but most of the parameter semantics are already captured in the schema. The default evidence-ranked behavior is also present in the schema's default value, so the description does not add significant new information.

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 specifies the action ('Get'), the resource ('full ranking for one of the 5 categories'), and the output characteristics ('ordered by composite score with all sub-scores visible'). It distinguishes itself from sibling tools like compare_agents and find_agents by focusing on category-based ranking. However, there is a minor inconsistency: the description says '5 categories' while the schema parameter mentions '4 AgentCrush categories', which could confuse clarity slightly.

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 is given on when to use this tool versus alternatives. The description does not mention situations where another tool would be preferable, nor does it reference sibling tools or provide any exclusion criteria. This is a clear gap for an agent deciding between ranking, search, or comparison tools.

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