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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the description is not the sole source. It still adds real context: pagination mechanics ('next_cursor identifies the next page; page size is not a history cap'), the separate paper:read permission requirement, and the provenance caveat that saved code is user-authored content.

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?

Four dense sentences, front-loaded with the primary action before paging and permission details. Nothing is padding, though 'immutable tested Python package' is slightly jargon-heavy for a code payload.

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 an output schema present, return values need no explanation, and annotations carry the safety profile; the description covers auth scope, pagination, and content trust. It stops short of defining 'owned run' or failure behavior, which leaves only minor gaps for a 4-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 0%, so the description must compensate and it only partly does. It explains kind (code/trades/equity), that the cursor value is the next-page token, and that limit bounds page size rather than total history, but run_id - a required parameter - receives no explanation at all.

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 names a specific verb and resource set - read code, page through trades or equity points - and scopes it to 'an owned run', which separates it from get_run_report and get_strategy. An agent can tell from the text alone which of the three data kinds this call serves.

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 by the kind enum and the phrase 'for an owned run', but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as get_run_report for summaries. The paper:read permission hint is a prerequisite, not a selection rule.

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