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 the return shape (trust_level enum, score, reasons, proven identities) that annotations cannot carry. Minor gap: no mention of what happens when no bot matches or when the profile is incomplete (the 'unknown' level is listed but not explained behaviorally).

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 sentences, no filler. The purpose and return contents lead, and the alternates (check_payment, then the id forms) follow — correct front-loading for a lookup tool.

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?

With no output schema, the description correctly compensates by enumerating the returned fields and trust levels, and all three params are addressed in context. Slightly incomplete on failure/unknown handling, but everything needed to make a correct call is present.

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 coverage is 100%, so the baseline is 3; the description still adds value by stating the two invocation modes as a real XOR (agent_id alone, or protocol + id) and clarifying that id is the wallet/ICP principal/DID/domain. That resolves the schema's bare "Or:" prefix into an actionable either/or.

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?

Specific verb + resource ("Look up a bot's full public trust profile") plus the exact contents returned: trust_level with its full enum, score, reasons, and proven identities. It also names the sibling it is not (check_payment) so an agent can disambiguate without opening a schema.

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?

Explicitly routes the payment case to check_payment with the trigger condition ("when you are about to pay a wallet"), which is exactly the differentiation an agent needs. It stops short of covering other ambiguities, e.g. whether this replaces or should follow search_bots when the agent id is not yet known, and what to do when the lookup comes back unknown.

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