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

Annotations already declare readOnlyHint, idempotentHint and a closed world, so the safety profile is covered. The description goes beyond that by disclosing a behavioral trait about the response itself – that it deliberately withholds original inputs, callbacks and requester identity – which is genuinely useful for interpreting results. It stops short of discussing polling cadence, expiry, or error states.

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 no padding; the core action is stated first and the caveat second. 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?

For a one-parameter, read-only, idempotent lookup with no output schema this is close to sufficient, but an agent still lacks any notion of what status values to expect, whether the status is final, or how to obtain the request_id. The privacy note is the only return-value hint provided.

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 parameter burden. Calling the value an 'opaque Broker status URL' usefully signals it is a token that must not be constructed or parsed, but it never says where the value comes from or reconciles with the schema's name of request_id (a dotted 36-char UUID pair).

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 (read) and resource (the Broker status URL for a request), so the agent knows this fetches the status of a previously submitted request. It does not explicitly contrast itself with siblings like request_capability, but the read-vs-write distinction is inferable from the verb.

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?

No when-to-use guidance, no mention of the companion tool that produces the request_id (request_capability), and no statement of when this is or is not the right call. The agent must infer that this is a follow-up poll after a request was submitted.

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