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

Annotations already declare readOnly/openWorld=false, but the description adds genuinely non-obvious behavior: the 8-K/A supersession rule (replaces only if it restates every matter, else both shown) and the 'only verified readings are shown' filter. It also explains the empty-result semantics, which is exactly the kind of context structured fields cannot carry.

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?

Front-loaded with the core purpose, then two sentences of caveats that each carry real information. The first sentence is long and clause-heavy, but every clause earns its place and nothing is redundant.

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 takes on the burden of describing the return shape (per-matter rows with For/Against/Abstain/Withheld/broker non-vote counts, outcome and quote, source filing) and the edge cases. An agent knows what it will get and how to interpret an empty response.

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 both parameters documented, so the schema does the heavy lifting. The description reinforces ordering ('latest meeting first') but adds no syntax or format detail for the ticker or meetings parameters beyond the schema. Baseline 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?

States a specific verb and resource (get a company's shareholder meeting vote results) and pins the exact data source (SEC 8-K Item 5.07), which no sibling tool covers. An agent can distinguish this from GetExecutiveCompensation or GetInvestorEventTranscript at a glance.

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?

Gives clear context: latest meeting first, 8-K/A replacement rules, and what an empty answer means. It does not name an explicit alternative tool or state when-not-to-use, but no sibling overlaps this data, so the routing risk is low.

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