getDistributionRecord

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

The description adds a rate limit of 50 req/s, which is a behavioral trait. However, without annotations, it does not state that the operation is read-only (though 'Query' implies it) nor disclose other behaviors like authentication needs or error handling. The description is adequate but not 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?

The description is concise with two sentences, no redundant information. It front-loads the purpose and rate limit. Loses a point for lack of structure (e.g., no separation of parameter info) but overall efficient.

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?

Given no output schema and 4 parameters with no description coverage, the description should have provided more details on return format, possible filters, or default behaviors. The vague 'etc.' leaves gaps, making it incomplete for a query 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?

With 0% schema description coverage, the description fails to explain the parameters. It only mentions the output fields, not what accountId, awardId, specCode, or withUsedAmount mean. This leaves the agent without semantic context for selecting parameter values.

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 clearly states the verb 'Query' and the resource 'voucher distribution records', listing specific fields like claim status, validity period, and consumed amount. This specificity distinguishes it from sibling tools, which are also query tools but for different resources.

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?

No explicit guidance on when to use this tool versus alternatives. The sibling tool list is extensive but the description provides no context for selection, no prerequisites, and no when-not-to-use conditions.

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