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

No annotations are provided, so the description carries the full disclosure burden. It does reveal the shape of returned data (per-version ratings, timeout/exception health, recent matches with replay/watch URLs), which is genuinely useful since there is no output schema, but it says nothing about access requirements, error behavior for unknown bots, or whether the result is live or cached.

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 short, but it is a bare noun-phrase fragment with no leading purpose statement; the reader only learns what comes back, not what the call does. Nothing is wasted, but the front-loaded element is the wrong one.

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?

For a one-parameter read tool with no annotations and no output schema, the description supplies only the return-content sketch. The essential pieces — that it takes a bot name and returns that bot's profile — are left implicit, so an agent cannot confidently select or invoke it without guessing.

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?

There is one required parameter, 'name', with 0% schema description coverage, and the description never mentions it or clarifies it is the bot name rather than an account or ladder name. With a single undocumented parameter the description should have compensated 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 is a list of returned data ('Ratings per version, health (timeouts/exceptions), recent matches with replay and watch URLs') rather than a statement of what the tool does. Combined with the name get_bot it is inferable that this retrieves a single bot's details, and the content does distinguish it from siblings like get_match or list_matches, but no verb or scope ('for a given bot name') is ever stated.

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 call this versus alternatives such as get_match, get_live, or list_matches, nor any prerequisite (does the bot need to be yours? must it exist?). The agent must infer usage from the name alone.

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