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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, but the description adds substantial context: data sources (SEC, House Clerk, Senate, OGE), filing lag ('days to months behind'), absence of prices or returns, the quoted nature of names and notes with a safety instruction, and the comparison logic for non-watched funds (including null-change behavior when only one report is held). This is far beyond what the annotations provide.

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 long and somewhat rambling, with redundancies such as 'There are no prices...' followed later by 'This answer carries no returns.' and 'Information, not advice.' It is mostly front-loaded with the purpose but would benefit from tighter organization and elimination of repeated caveats.

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 no output schema, the description carries the burden of explaining return values and it does so at a high level (opened, sold, added, trimmed, largest holdings) and even names a field (compared_with_quarter_end). It also covers data provenance, staleness, and comparison logic. Missing only precise field shapes or counts, but it is largely complete for a complex 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 coverage is 100% and the single slug parameter is fully described in the schema. The description adds only that slugs can be found via search_funds, which is a minor contextual hint. Baseline 3 is appropriate when the schema already does the heavy lifting.

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 resource (one money manager's quarterly report) and enumerates the changes (opened, sold, added, trimmed, largest holdings), which distinguishes it from generic filing searches. It references search_funds as the way to find slugs, but doesn't explicitly contrast with other sibling tools like get_signals or get_record.

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?

Mentions that it covers 'Any fund Aeon holds: the 16 it watches and the largest filers' and that slugs come from search_funds, which gives some context. However, there is no explicit when-to-use guidance, no exclusions, and no comparison to alternative tools that might also return fund or filing data.

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