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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real context by revealing the payload is a comparison time series against S&P 500 and Pelosi, but it says nothing about granularity, defaults, or how roi_mode changes results.

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 filler; the resource and the two benchmarks arrive immediately. It is efficient but leaves obvious room for a follow-on usage sentence that would earn its place.

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 no output schema, the description does the key work of characterizing the return payload as a daily time series with benchmark comparisons. Remaining gaps (default date range, granularity, meaning of roi_mode) are modest for a zero-required-parameter read tool.

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 each parameter (max_date, min_date, roi_mode enum) is already documented. The description adds nothing about date-range behavior or what 'delay-adjusted' ROI actually means, 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?

The description states a specific verb (Get) and resource (Donald Trump's portfolio daily performance time series), plus the comparison baselines (S&P 500, Pelosi). It distinguishes itself from generic siblings like get_politician_portfolio_performance by naming the subject, though it never contrasts with close siblings such as get_trump_admin_performance or get_trump_mentions_performance.

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 only implied by the tool name and resource subject; there is no explicit statement of when to pick this over get_trump_admin_performance, get_trump_holdings, or get_politician_portfolio_performance. No exclusions, prerequisites, or alternative routing are given.

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