export_portfolio

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint= false, covering safety and side effects. The description adds that output is JSON and supports filters, but does not disclose potential limits like pagination, max results, or rate limits, which are relevant for an export operation.

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 fluff. The first sentence is action-focused and conveys the core purpose. The second sentence is slightly redundant but adds clarity. Could be more concise by merging.

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?

Given the presence of output schema and comprehensive annotations, the description is adequate but lacks details on export-specific behavior such as pagination, data limits, or whether the export includes all historical data or a subset.

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% with all 7 parameters described. The description simply summarizes them as 'optional query filters', adding no new semantics beyond what is in the schema. Baseline of 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 clearly states the tool exports portfolio activities/transactions data as JSON. This is a specific verb+resource+output, distinguishing it from sibling tools like get_portfolio_details or get_portfolio_holdings which likely provide different data or formats.

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 implies usage for exporting historical transaction data with optional filters, but no explicit when-to-use or when-not-to-use guidance is provided. With many sibling tools, comparisons or exclusion criteria would improve clarity.

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