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

Annotations already declare read-only, idempotent, non-destructive, so safety is covered. The description adds value annotations don't: the output is a daily time series benchmarked against the S&P 500, which tells the agent what it will get back. It doesn't mention date-range defaults or whether missing dates are interpolated, but it is well ahead of the annotation-only baseline.

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?

Two sentences, no filler, with the core purpose front-loaded and the parameter hint second. Every sentence carries information the agent needs.

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's note that results are a daily time series compared to the S&P 500 is doing real work. It is slightly short on what the default date window is and how the benchmark comparison is represented, but an agent has enough to call it correctly.

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% and already documents max_date, min_date, and the portfolio enum with its default, so the description largely restates structured data. It confirms the enum intent ('pick the slice') but adds no date format or range semantics beyond the schema.

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 the daily performance time series for a portfolio of public companies tied to Trump Accounts and the White House Ballroom fundraising drive.' This clearly separates it from siblings like get_trump_sponsors_holdings (holdings, not performance) and get_trump_admin_performance (different portfolio).

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 says how to slice results via the portfolio param, which implies the 'all' vs subset choice, but never states when to reach for this tool over get_trump_performance, get_trump_admin_performance, or get_trump_sponsors_holdings. Usage is inferable rather than explicit.

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