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

Annotations already indicate readOnly and openWorld behavior. The description adds important context beyond annotations: admin-only restriction, bearer token requirement, and the note that provider operations/credentials remain in the existing middleware service. No rate limits or output format details, but output schema exists, so this is sufficient.

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?

Four efficient sentences, front-loaded with purpose and usage. Every sentence contributes: scope, prerequisite, authentication, and boundary. No wasted words.

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 the read-only nature, single optional parameter, and presence of an output schema, the description is nearly complete. It covers purpose, usage, authentication, and a relevant boundary. The only significant gap is the unexplained 'account_id' parameter, but overall it supplies enough context to call the tool correctly.

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 0% for the single optional parameter 'account_id'. The description does not mention 'account_id' at all, leaving the agent with no guidance on whether it filters results, what omitting it does, or what values are valid. Since coverage is low, the description should have compensated but does not.

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?

States a specific verb ('read') and precise resources: 'enabled provider accounts, capabilities and transaction input schemas'. This clearly distinguishes it from sibling tools like middleware_submit_transaction and middleware_get_transaction, which handle other aspects of the middleware workflow.

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 'Use this before middleware_submit_transaction', giving a clear workflow prerequisite. Also states 'Middleware admin only' and requires a static admin bearer token, providing actionable conditions for use.

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