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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. However, the description adds almost no behavioral context: it does not explain what 'rank' produces (e.g., sorted list, scores), how the 5.2 EARN engine behaves, or any side effects. The opaque '5.2 EARN engine' reference actually obscures behavior rather than clarifying it.

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 a single short sentence with no filler words, so it is technically concise and front-loaded. However, it is under-specified: the '5.2 EARN engine' phrase adds jargon without explanatory value, and the brevity leaves out essential information. Minimalism here is not appropriately sized.

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?

For a tool with 4 undocumented parameters, no output schema, and a vague proprietary engine reference, one sentence is grossly insufficient. The agent cannot determine expected input formats, how parameters influence ranking, what the returned data looks like, or when this tool is preferable to its many siblings.

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 information about the four parameters (goal, limit, skills, currency). With zero schema documentation and zero compensation in the description, the agent cannot infer parameter meaning, formats, or relationships from either source.

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 states a specific verb ('Rank') and resource ('opportunities') and names the mechanism (5.2 EARN engine), so it is not a tautology. However, it does not clarify what 'opportunities' are or how this ranking differs from the many sibling tools that also list, search, or rank opportunities, leaving its purpose ambiguous.

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 guidance is provided on when to use this tool versus alternatives such as search_global_earn, list_build_opportunities, or rank_profitable_opportunities. The phrase 'using the 5.2 EARN engine' vaguely implies a particular ranking approach but does not state a condition, context, or exclusion.

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