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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing further — no mention of pagination behavior (limit/cursor), snapshot-date semantics, or what roi_mode changes about results, even though that is the one behavioral knob an agent could get wrong.

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 front-loaded sentence with no padding. It is efficient, though the brevity borders on under-specification given the pagination and ROI-mode affordances the tool exposes.

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?

With five parameters, a cursor-based pagination scheme, a date-range filter, and an ROI mode enum, a one-sentence description is thin — but no output schema exists and the schema itself fully documents every parameter. It is adequate but leaves the agent to figure out default paging and what the returned holdings represent (value, ROI, disclosure date).

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 100%, so all five parameters (limit, cursor, max_date, min_date, roi_mode) are already documented in the schema. The description contributes no additional meaning about filtering, date semantics, or ROI mode, so the baseline 3 applies.

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?

States a specific verb ('Get') and a well-scoped resource: defense sector holdings held by Congress members. The two qualifiers (sector and holder type) make the intent clear, but it does not explicitly distinguish itself from the closely related sibling get_politician_portfolio_holdings, leaving the agent to infer that this is the defense-only slice.

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?

There is no guidance on when to use this tool versus get_politician_portfolio_holdings, get_defense_performance, or get_defense_performance-adjacent siblings. The agent must infer selection criteria from the name alone, and no exclusions or prerequisites are stated.

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