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

With readOnlyHint already set, the description still adds useful behavioral context: broker-read failures are visible tool errors, a later analysis execution refreshes its broker endpoint, and observation/retrieval timestamps are not market-price timestamps. Some sections are workflow instructions rather than direct tool behavior, but the key behavioral constraints are disclosed.

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 purpose is front-loaded, but the definition is a dense wall of caveats, anti-hallucination rules, and downstream workflow instructions. Many sentences govern result interpretation rather than helping select or invoke this tool, so it is not appropriately sized for a tool definition.

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?

For a tool with no output schema and only readOnlyHint, the description covers many important return and provenance details, including observation counts, datasetId registration, timestamp caveats, and broker-read failure behavior. It is not fully complete about the returned row shape, but it provides substantial context for correct use.

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 0%, so the description must carry parameter meaning. It explains frequency bucket behavior ('all', 'hour', 'day'), start/end window constraints, limit bounds, and the distinction between fullDatasetObservationCount and count, though it omits the expected date format for start/end and does not describe deploymentId beyond the title.

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 first sentence states a specific verb and resource: it returns owned linked-account history plus a fresh direct broker balance. It also explicitly distinguishes this from strategy-attributed or cash-flow-adjusted performance and names show_bot_activity as a sibling alternative.

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?

It gives explicit routing guidance: use show_bot_activity first for a current account report, and use this reader for a requested historical graph or benchmark comparison. It also points to run_data_analysis for portfolio-movement calculations, naming the alternative tool and condition.

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