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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the verdict is rule-based and deterministic ('payouts never change it'), it returns the exact sourced facts and rule ids behind the verdict, and it explicitly disclaims being a rating or advice.

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 dense sentences with no filler, front-loading the resource and its verdict taxonomy before the disclaimer. Slightly overloaded with parenthetical enumerations, but every clause carries information.

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 enumerates the possible verdict values and notes that sourced facts and rule ids are returned, which an agent needs to interpret results. The remaining gap is slug semantics and the absence of routing guidance versus get_bot/check_bot.

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 single parameter 'slug' has 0% schema description coverage, so the description carries the burden. 'For a bot' weakly implies the slug identifies the bot being reported on, but the description never states the format, source, or lookup semantics of the slug, leaving the parameter under-specified.

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?

States a specific verb+resource: a rule-based BotOrNot report card for a bot, and even enumerates the possible verdicts (Clear record, Caution, Red flags, Closed, Limited data). It does not explicitly contrast with close siblings like get_bot or check_bot, so an agent must infer the boundary, but the resource and output nature are unambiguous.

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 when-to-use or when-not-to-use guidance, and no named alternative among siblings such as get_bot or check_bot. The clause 'Not a rating or investment advice' constrains interpretation of the output rather than telling the agent when to select this tool over its neighbors.

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