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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing. It does not say whether retrieval requires authorization, whether access is audited, whether secret material is returned in plaintext, or what happens when the query matches nothing. For a credential-vault read these are significant omissions.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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 a security-sensitive vault read with no annotations, no output schema, and an undocumented optional parameter, the definition is not complete enough. An agent cannot determine what it will receive back or whether calling it has side effects such as audit logging or secret exposure.

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% for the single `query` parameter, so the description must compensate and does not. It never says whether `query` is a token name, label, substring match, or free-text filter, nor what an omitted `query` (it is not required) returns.

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 ("Retrieves") and a specific resource ("stored long-lived tokens") plus its source ("the vault"), so the agent knows what kind of operation this is. It does not differentiate itself from siblings such as vault_lookup or credential_broker, which plausibly overlap, so it stops short of a 5.

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?

There is no explicit when-to-use guidance, no exclusions, and no named alternative. The adjective "long-lived" implicitly contrasts with short-lived or refreshable credentials (cf. oauth_refresh), but the agent is left to infer that boundary rather than being told it.

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