Get fantasy position rankings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the ordering is by points per game, which is useful. However, it does not disclose what the response looks like, whether it returns a list object, or any pagination or error behavior. For a read-only query this is a moderate gap, but not critical. The lack of annotation support limits transparency.

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 concise, using two sentences that front-load the primary resource and ordering, then provides usage guidance. It wastes no words, and the structure is clear. It could be slightly more structured by separating the usage hint, but it is effective and easy to parse.

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 relatively simple tool that returns a list of rankings, the description covers the essential aspects: what it returns (rankings ordered by points per game), the valid positions, and typical use cases. The absence of an output schema is acceptable because the return shape is likely straightforward and inferable. It does not mention pagination or response format, but those are not strictly required for a basic query. Overall, the description is adequately complete for its complexity.

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 provides descriptive text for all three parameters (position, limit, scoring_format) with enums, defaults, and explanations, yielding 100% schema description coverage. The tool description adds little beyond the schema: it restates the position list and the ordering note, but the schema already covers the meaning and defaults. Since the schema is thorough, a baseline of 3 is appropriate, and the description contributes marginal extra value.

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 the verb 'get rankings' and the resource (position, scoring format) and specifies the ordering by points per game. It also lists the accepted positions. However, it does not explicitly differentiate itself from sibling tools like get_positional_scarcity, relying on the reader to infer the difference. Overall it is specific and unambiguous about what it does.

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?

The description provides explicit usage examples: "Use this for 'who are the best X' and draft board questions." This gives clear context for when to invoke the tool. It does not, however, mention when NOT to use it or point to alternatives for different kinds of queries (e.g., comparing players or checking scarcity), so some situational guidance is missing.

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