list_stewardship_reports

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

No annotations provided, so description carries full burden. It states it lists reports and requires Enterprise tier, but does not disclose consequences of non-enterprise access, rate limits, pagination, or whether any data is mutated. Basic transparency but leaves gaps.

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?

Single sentence with no extra words, front-loaded with key information: action, resource, constraints, and output details.

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 list tool with no parameters and no output schema, description covers purpose, output fields, user scope, and tier requirement. Could mention pagination or ordering, but generally complete.

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?

No parameters, schema coverage 100%. Description adds value by specifying return content (vote counts, compliance rates, period dates) beyond the empty schema.

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 'List FMA-compliant stewardship/voting-record reports' with output specifics (summaries, vote counts, compliance rates, period dates) and distinguishes from sibling 'get_stewardship_report' by being a list operation.

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 says 'for the authenticated user' and 'Enterprise tier required', giving clear context. Does not mention when not to use or explicitly name alternatives, but sibling name implies that for a single report use get_stewardship_report.

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