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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds behavioral context by stating it compares the latest and prior quarter and enumerates the output types (positions, exits, weight changes, counts). This goes beyond simple repetition of annotations and gives the agent a clear expectation of the result nature.

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, dense sentence with no filler. It front-loads the core purpose ('Compare the latest and prior quarter') and packs in the key details without redundancy. Every part of the sentence contributes meaning.

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 description gives a solid overview of the output but omits parameter explanations and does not specify the exact response structure (no output schema provided). Given the tool has four parameters with zero schema descriptions, the description is not fully sufficient for an agent to call it correctly without additional schema inspection. It covers the 'what' but not the 'how' or 'format'.

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 by explaining parameters. It only hints at 'funds' via 'up to 50 funds' and 'ranked by the provider' implies the 'rank' parameter, but it does not explain 'limit' or the 'quarter' format (e.g., YYYYQ#). The description adds minimal value for parameter understanding, leaving agents to infer from defaults and enums.

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 'Compare', the resource '13F crowding', and the scope 'across up to 50 funds ranked by the provider', followed by specific outputs ('new positions, exits, aggregate weight changes and the fund count'). This distinguishes it from sibling tools like sec.thirteenf_holders, which focus on individual holdings rather than aggregate crowding.

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 implies when to use this tool (for comparing quarterly crowding changes) but does not explicitly mention alternative tools or conditions when not to use it. It lacks contrast with siblings such as sec.thirteenf_holders, so usage guidance is implied rather than explicit.

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