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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description goes beyond this by disclosing that only active, current insights are ever returned, that detail=full changes the payload, that every response is historical aggregated data, and that it is descriptive only and never a recommendation. No contradiction exists.

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 description is dense but well organized: a one-line summary, filter details, returned-field semantics, a behavioral caveat, then workflow placement. Every sentence contributes, though there is slight redundancy between 'historical performance data' in the first line and 'historical collective performance data' later.

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 an output schema and strong read-only annotations, the description covers purpose, filter semantics, output contents, safety behavior, and usage workflow. The main missing pieces are an explanation of caller_id and the default behavior when no filters are provided, which keeps it from being fully complete.

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 carries the parameter-documentation burden. It clearly defines asset (mint/symbol), names strategy_type as a filter, gives a full enum for insight_type, and explains the effect of detail=full. However, caller_id is never explained, and strategy_type valid values are not enumerated, leaving partial gaps.

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 opens with a specific verb+resource pair: 'Fleet-wide collective insights, historical performance data (free read).' It then enumerates the exact insight types and fields returned, and positions the tool within the INTELLIGENCE workflow alongside get_market_briefing / get_consensus, which differentiates it from the many other get_* read tools in the sibling list.

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 'Workflow: INTELLIGENCE step' sentence explicitly tells the agent when to use this tool: for fleet-wide context before sizing or creating strategies, alongside get_market_briefing and get_consensus. The 'never a recommendation' caveat also clarifies that output should not drive direct execution. However, it does not provide explicit when-not-to-use guidance or name alternatives to prefer in specific cases.

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