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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the valuable access-control constraint (admin only) but says nothing about error behavior for unknown contact_id or whether results differ from the registrar-side contact store.

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?

One sentence, no filler, with the access restriction front-loaded before the operation. It is arguably too terse for the ambiguity it leaves, but nothing in it is wasted.

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 need no explanation, and the admin gate is stated. Still, for a tool sitting alongside a similarly named get_contact, the description leaves the agent guessing about store differences and failure modes.

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 parameter, so the description carries the burden. It does tell the agent that contact_id refers to a middleware-local contact id (a meaningful disambiguation from other id spaces in the sibling set), but gives no format or example.

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 resource (a local middleware contact) plus the lookup key (contact_id). The qualifier 'local middleware' does distinguish it from the sibling get_contact, though the distinction is only implicit rather than spelled out.

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 'Middleware admin only' clause establishes a prerequisite and audience, which is real usage guidance. However, it never says when to pick this over get_contact or list_contacts, nor what to do if the contact is not found in the middleware store.

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