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

With no annotations, the description carries the full burden. It adds useful context: data is sourced from SEC EDGAR, every row links to its filing, and the data is free under CC BY 4.0. It does not disclose freshness, update cadence, rate limits, or explicit read-only behavior, but for a simple GET-style data tool the provided context is reasonable.

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 extremely tight, with each phrase delivering distinct information: content, form type, source, row-link behavior, and licensing. It is front-loaded and contains no filler or repetition.

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?

For a one-parameter list retrieval tool with no output schema, the description covers the core invocation needs: what data is returned, where it comes from, that rows link to filings, and that access is free. It could mention data coverage or refresh behavior, but nothing essential for calling the tool is missing.

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?

The input schema has 100% coverage for the only parameter, limit, including default, ceiling, and response indicators. The description adds no parameter-specific meaning, but it does not need to because the schema already fully documents the parameter.

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 identifies the resource as Annual Meetings backed by SEC Form DEF 14A definitive proxy statements, sourced from SEC EDGAR. This makes the returned data concrete and distinguishes it from sibling tools like get_mergers or get_breaches. It relies on the tool name for the action verb, but the resource is specific and clear.

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 description implies the tool should be used when an agent needs annual meeting or proxy statement data. It does not explicitly state when not to use it or name alternative tools, but the subject matter is distinct enough to infer the intended use case from the sibling list.

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