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

Annotations only supply readOnlyHint and openWorldHint; the description adds real context beyond them — an admin-only access restriction, the meaning of each terminal/non-terminal status, and the operational rule that non-succeeded states must not cause a retry/duplicate order. It stops short of stating behavior for unknown transaction_ids or error responses.

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 with no filler: the first front-loads the access restriction and the verb+resource, the second packs the status semantics, the duplicate-order prohibition, and the authcode follow-up. Every clause earns its place.

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?

An output schema exists, so return-value explanation is unnecessary; the description covers access control, status interpretation, and the authcode follow-up. Minor gaps: where the transaction_id originates and what happens on a not-found or unauthorized lookup.

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?

Only one parameter and zero schema description coverage, so the description carries the burden. It ties the call to 'transaction_id' but adds no format, provenance (e.g. from middleware_submit_transaction), or validation detail beyond the field name itself.

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?

Specific verb+resource: 'read a middleware transaction's status and result by transaction_id', which is clearly a single-record lookup. It implicitly contrasts with the sibling middleware_list_transactions via 'by transaction_id', though it never names that sibling explicitly.

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?

Gives a hard audience gate ('Middleware admin only') and concrete downstream guidance: 'succeeded confirms completion; pending_provider, outcome_unknown and manual_review must not trigger a duplicate order.' It also routes to the alternative middleware_get_transaction_secret for authcodes. No explicit when-not guidance versus middleware_list_transactions, hence not a 5.

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