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

With no annotations provided, the description carries the full burden of behavioral disclosure. "Looks up" weakly implies a read, but nothing is said about permissions or authentication, whether the lookup is safe/non-destructive, what happens for an unknown account, or what the record contains.

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?

It is a single front-loaded clause with no filler sentences. Brevity is not the problem here; the gap is that the words present are too thin to be actionable.

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?

No annotations, no output schema, and an undocumented required parameter leave the agent without enough to call this confidently or interpret the result. A lookup tool with a decoy framing especially needs a note on what is returned and whether it is a real credential.

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 required parameter "account", and the description adds no clarification of what identifier form is expected. Because structured data gives the agent nothing, the description needed to compensate and does not.

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 supplies a verb and a resource ("looks up a synthetic credential record"), so the basic action is identifiable. However, the parenthetical "(research decoy)" makes the resource ambiguous rather than more precise, and nothing distinguishes this lookup from siblings like token_vault or credential_broker.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer usage entirely from the one-line purpose, with no signal about why one would pick this over token_vault or credential_broker.

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