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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false; the description adds valuable behavior beyond these: it clarifies the meaning of 'two report quarters' and defaults, and specifies the exact output structure (four ranked lists with issuer, CUSIP, value in both quarters, and dollar delta). No contradictions with annotations are present.

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, front-loaded paragraph that leads with the core purpose, then gives usage, defaults, and output details. Each sentence contributes, though the 'newsletter primitive' phrase is somewhat colorful; it still earns its place by reinforcing the change-vs-snapshot distinction. Overall, it is appropriately concise for the information it conveys.

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?

No output schema exists, so the description compensates by fully specifying the return format: four ranked lists with issuer, CUSIP, value in both quarters, and dollar delta. It also covers default quarter behavior and parameter usage, making it sufficiently complete for an agent to invoke the tool correctly without additional documentation.

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 coverage is 100%, but the description adds semantic meaning by explaining the relationship between quarter and compare_to (later vs earlier quarter) and their defaults. It also provides a format example (YYYY-MM-DD). This exceeds the baseline for high schema coverage by contextualizing the parameters without repeating schema text.

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 identifies a specific verb and resource: it reports what a single institutional manager NEW-ed, EXITED, INCREASED, or DECREASED between two 13F quarters. The phrase 'a portfolio snapshot is not news, a change is' explicitly distinguishes this tool from snapshot-oriented siblings like manager_portfolio, making the tool's unique value clear.

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 states when to use the tool (for changes, not snapshots) and describes the core usage pattern: provide a manager name and optionally two report quarters. It explains default quarter selection behavior. It does not explicitly name alternative tools or edge cases where the tool should not be used, but the conceptual contrast with snapshots provides adequate guidance.

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