Polyrank Smart-Money Report archive

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

Annotations (readOnlyHint: true, openWorldHint: true) already indicate read-only and dynamic data. The description adds that the output is a list of report ids/weeks with summaries, which provides behavioral context about the return format. It does not disclose other traits like pagination or latency, but with annotations covering safety, this is adequate.

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?

Two sentences with no wasted words. The purpose is front-loaded and the instruction for fetching a full report is efficiently included. Every sentence serves a purpose.

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 simple listing tool with one optional parameter and no output schema, the description provides enough context: it explains what the output contains (list of report ids/weeks with summaries) and how to get more details. Annotations cover read-only and dynamism. No gaps remain.

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 already fully documents the only parameter 'limit' with description, min, max, and default (100% coverage). The tool description adds no additional explanation for the parameter, so it relies on the schema, making a baseline score of 3 appropriate.

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?

Description clearly states the tool lists Polyrank weekly Smart-Money Reports with ids/weeks and summaries, and directly differentiates itself from the sibling tool polyrank_get_smart_money_report for fetching a full report. The verb 'list' and resource 'archive of reports' are specific.

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?

Provides clear context for when to use this tool (to get a list of reports) and explicitly mentions the alternative polyrank_get_smart_money_report for fetching a full report. However, it does not state any preconditions or when not to use this tool.

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