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

Adds real context beyond the annotations: the admin-only authorization requirement and the fact that this returns a cached projection rather than live provider data. However, the "submit action=refresh" instruction contradicts the actual one-parameter schema, muddying rather than clarifying behavior.

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 short sentences with the admin restriction front-loaded and no filler. The second sentence, however, spends space on a refresh action this tool cannot perform, which is wasted budget.

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 values needn't be explained. What is missing is the delegation path for the refresh workflow (which tool actually performs it) and any semantics for the single undocumented parameter, both of which the description raises but does not resolve.

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 description coverage is 0%, so the description must carry the meaning of domain_id, but it only restates the name. It does not say what format the ID takes, whether it matches the ID used by get_domain_status/get_domain_audit_log, or where to obtain it.

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 and resource ("read the middleware's domain projection by domain_id") and adds a clear access qualifier ("Middleware admin only"). "Projection" is jargon, and the description never explicitly contrasts this with the sibling get_domain_status, so an agent must infer which one to call.

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?

The only conditional guidance is "For a live provider refresh submit action=refresh first," but this tool's schema has no action parameter, so the instruction cannot be executed here and likely belongs to a sibling such as middleware_submit_transaction. It never names alternatives like get_domain_status for live data, leaving the core choose-which-tool decision unresolved.

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