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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely valuable context beyond that: the trust semantics of the badge ('vouched by members, reviewed by the Doorman') and an explicit disclaimer that it is 'not a security audit and not a guarantee', which shapes how an agent should weigh the result.

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-load the action and its outputs, then the trust caveat. 'Read-only' slightly repeats the annotation but does no real harm; otherwise it is efficient.

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?

There is no output schema, yet the description names the returned fields (signed statement, status with valid/expired/revoked, house public key) and explains what the badge does and does not attest. For a one-parameter read tool this is nearly complete; only explicit sibling routing is missing.

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 100% and the single agent_id parameter is fully documented in the schema (br_ prefix plus 16 characters). The description adds no parameter-level detail, so the baseline 3 applies.

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 ('Check') and resource ('Vouched by the Doorman' badge) and enumerates the returned artifacts (signed statement, status, public key). It implicitly distinguishes itself from siblings like backroom_lookup_agent by focusing on badge verification, though it never names an alternative.

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 'Check an agent's ... badge', but there is no explicit when-to-use, when-not-to-use, or routing guidance relative to backroom_lookup_agent or backroom_doorman. The agent must infer the trigger condition.

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