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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds the useful behavioral detail that output is a daily series benchmarked against the S&P 500, but says nothing about pagination, date-range defaults, or the empty/error case for a politician with no holdings.

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 sentence with no waste, and the key scope and benchmark are front-loaded. It is efficient but arguably too terse for a 4-parameter tool with no output schema.

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?

There is no output schema, so the description carries the burden of explaining return shape; it does state the output is a daily time series with S&P 500 comparison, which is the essential piece. Still missing date-range defaults, roi_mode semantics, and whether both series are returned, which leaves gaps for correct invocation.

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 every parameter (max_date, min_date, roi_mode, politician_bioguide_id) is already documented in the schema. The description adds no syntax, defaults, or meaning beyond what the schema provides; 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 and resource ('Get daily portfolio performance time series') plus scope ('politician or group') and a benchmark ('compared to S&P 500'). It is distinguishable from siblings like get_politician_portfolio_holdings and get_trump_admin_performance, but does not explicitly name the alternative to route away from.

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?

Usage is implied: performance time series vs. holdings or trades. However, there is no explicit when-to-use/when-not-to-use guidance and no named alternative (e.g., use get_politician_portfolio_holdings for current positions), leaving routing to inference.

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