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

The annotations already declare readOnlyHint, non-destructive, and openWorld, so the safety profile is covered. The description adds real behavioral value by specifying the returned payload shape (lines, taxes, terms, payments, status) and the underlying GET route, though it says nothing about auth, pagination, or errors.

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 compact sentences, front-loaded with purpose and payload contents, ending with the endpoint for orientation. No filler.

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 two-parameter read tool with full schema coverage and readOnly annotations, the description covers purpose, scope, and roughly what comes back. Slightly short only on how an agent should obtain a valid transaction_id.

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 100% and the enum already documents every allowed type value, so the schema does the heavy lifting. The description's enumeration of document types mirrors the enum without adding syntax or constraints beyond it, which is the baseline 3 case.

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 names a specific verb ('Get') and resource ('one sales document in full'), enumerates the concrete document types covered, and lists the data returned (lines, taxes, terms, payments, status). An agent can distinguish it from bukku_list_sales_documents purely on the 'one document in full' scope.

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?

Usage is implied by the 'one document' phrasing and the required type/id pair, but there is no explicit when-to-use guidance, no prerequisite such as needing an id from the list endpoint first, and no sibling alternative is named.

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