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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is interpretive: dates filter SEC filing_date, announcements are not effective dates, registrant may differ from employer, and duplicate sources are not distinct changes. Those are genuinely useful domain caveats beyond the annotations, but it says nothing about result shape, volume, ordering, or limits, so it is solid rather than rich.

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 short lines, front-loaded with the core action and scope, then the parameter semantics, then the interpretation caveats. Every fragment carries information, though the phrasing is clipped to the point of reading like internal notes ('preserve role, employer, interim status...') rather than an instruction to the calling agent.

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, the description is not obliged to explain return values, and it covers the essential inputs plus the interpretive pitfalls an agent would otherwise get wrong. The remaining gap is operational behavior - pagination, result ordering, or caps - which matters for a source-mention listing tool but is a minor omission given the schema richness.

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 the load, and it largely does: it defines cik as a ten-digit registrant CIK and explains that start/end filter SEC filing_date in YYYY-MM-DD form. That supplies format and semantics the bare schema lacks, though it never clarifies inclusive/exclusive bounds or null/default behavior for the optional date parameters.

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 gives a specific verb and resource ('Read executive/board source mentions') and scopes it to a 'ten-digit registrant CIK', so the agent knows this returns leadership-related source documents rather than prices or filings. It stops short of naming the sibling it most resembles (get_leadership_passage) or stating how the two differ, so differentiation is only implied by 'source mentions'.

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?

There is no explicit statement of when to use this tool versus get_leadership_passage, get_timeline, or list_leadership_companies. The cautions ('Announced does not mean effective', 'repeated sources are not distinct changes') frame how to interpret results but never say which query should route here, leaving the choice to inference from the tool name.

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