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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the resource shape and endpoint but says nothing about pagination behaviour, default ordering or result volume, which matters for a 10-param list tool.

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?

Two sentences, the returned fields front-loaded and the filter options and endpoint following. No wasted text, though the endpoint fragment could be dropped without loss.

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 filter-driven list tool with no required parameters and no output schema, naming the returned fields covers the main missing piece. Pagination and default ordering are handled by the schema descriptions, so the definition is close to sufficient.

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 70%, so most parameters are documented in the schema. The description's mention of payment status values adds little because those enums are already in the schema, and it does not clarify the two distinct status concepts or the sort parameters.

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 states a specific verb and resource ('List purchase bills'), names the returned fields (number, date, supplier, amount, balance, payment status) and the endpoint. It does not distinguish itself from the close sibling bukku_list_purchase_documents, which is the main remaining gap.

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?

It lists the available filter dimensions (date, supplier, payment status, keywords), which implies how to narrow results. But it never says when to prefer this over bukku_list_purchase_documents or bukku_get_purchase_document, nor does it state any prerequisites.

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