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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the response includes a link to the full methodology, which is genuinely useful context, but says nothing about response shape or whether both ranking types can be retrieved together.

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?

A single sentence with no filler; the substantive content (pillars, weights, criteria, methodology link) is front-loaded and the qualifier about ranking type follows naturally.

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 one-parameter, read-only lookup with no output schema, the description conveys what the caller gets back and the scope of each ranking type. Only minor gaps remain — whether the methodology is shared across both types and the exact return structure.

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 — and it does partially by phrasing the resource as covering 'trading schools or of prop firms', which maps directly onto the schools/prop_firms enum. It still does not state that the parameter is required or what happens if omitted.

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 names a specific resource — pillars, weights and criteria of the Tradoshi 2027 ranking — plus the methodology link, which is far more informative than the title alone. It does not explicitly contrast itself with siblings like get_rankings, but the resource is distinctive enough to distinguish it.

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?

Usage is only implied: an agent can infer it should call this when it needs to explain or justify how a ranking was produced. There is no explicit when-to-use statement, no mention of when not to call it (e.g. use get_rankings for actual scores), and no named alternative.

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