agm_result

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

With no annotations, description discloses data source (KIND crawling), receipt number conversion, and no-data condition for unended meetings. Does not state read-only nature but implied.

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?

Structured into clear sections (desc, when, rule, ref, Args). Every sentence adds value, no fluff.

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?

Covers purpose, usage, behavior, parameters, and references sibling tools. Output schema exists, so return values not needed. Complete for this 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?

Despite 0% schema description coverage, the tool description contains an Args section explaining each parameter (ticker, dates, format) with defaults and formats, fully compensating.

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?

Description clearly states it provides shareholder meeting voting results including pass/fail per agenda, approval rates, and estimated attendance. Differentiates from sibling agm_post_analysis by noting standalone use when only voting results are needed.

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?

Explicitly specifies when to use (viewing voting results) and when not (for broader analysis, use agm_post_analysis). Provides data source rule and behavior when meeting not ended.

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