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. It describes what the tool returns, that it relies on previously fetched profile signals, and that it may surface same-name accounts. It does not mention potential side effects, auth requirements, or data freshness, but as a read-style lookup tool the disclosed behavior is reasonably transparent.

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?

The description is longer than average but front-loads the core purpose with the 'ANTI-IMPOSTOR' framing and then packs in return details, a concrete example, and a prerequisite. Some decorative phrasing could be trimmed, but every substantive point 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?

The tool has one parameter, an output schema, and no annotations; the description covers the prerequisites, the main return values, and the disambiguation use case. It is missing an explicit handle format clarification, but otherwise an agent has enough context to invoke it correctly.

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?

The schema has one required 'handle' parameter with no description coverage, and the description does not explicitly explain how to format the handle or whether to include the '@' prefix. The example '@aleabitoreddit' hints at the account identifier but leaves ambiguity. Because schema coverage is 0%, the description needed to compensate with explicit parameter guidance and only partially does.

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 states a specific verb ('Returns') and a clear resource: the account's authenticity signals, credibility score, permanent account id, and same-name accounts. It explicitly frames the tool as an anti-impostor check, which distinguishes it from sibling analyst tools like analyst_views or analyst_track_record. The use-case example ('tell the real @aleabitoreddit from a 1-tweet impostor') makes the purpose unmistakable.

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 description gives a clear prerequisite: the analyst must have been fetched once via analyst_views. It also illustrates when an agent would want this tool, such as when a user searches a name and needs disambiguation. It does not explicitly list when not to use it, but the prerequisite and use-case provide enough context.

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