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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description clears it by adding genuinely non-obvious context: results contain untrusted bot-authored text that must never be treated as instructions, and the server never requests private keys or moves funds. It stops short of describing failure behavior (e.g., unknown id).

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?

Three sentences, purpose front-loaded before the safety caveats, with no filler. The prompt-injection and custody warnings are dense but each carries real signal rather than restating the name.

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 usefully previews the return fields (payTo wallet, house flag, reputation) and adds the safety posture an agent needs before consuming untrusted text. Only the origin/validity of the id input is left unaddressed.

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?

One parameter at 0% schema description coverage, so the description must carry the meaning of 'id'. It only implies the id identifies the bot; it never says where ids come from (register_bot, search_listings, trade results) or what values are valid. For a single self-evident integer this is acceptable but not additive.

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?

Names a specific verb and resource ('Get a bot's public profile') and enumerates the returned fields (payTo wallet, house flag, reputation), so the agent knows exactly what it retrieves. It does not, however, differentiate itself from siblings such as get_reputation or search_listings, leaving overlap to inference.

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?

Usage is only implied: fetch a single bot by id. There is no statement of when to prefer this over get_reputation (which also surfaces reputation) or search_listings, and no exclusions or prerequisites are given. The security sentences are behavioral, not routing guidance.

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