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

With no annotations, the description carries the burden of behavioral disclosure. It discloses the scope (only the caller's own bots), the included bot types (personal, incubating, live), the included data (live engine stats and gamified card ratings), and the return format (JSON array).

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 concise and well-structured: a clear one-line purpose, a short contextual caveat, and a focused parameter note. Every sentence earns its place and the most important information is front-loaded.

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 description gives enough information to invoke the tool correctly: ownership scope, eligibility categories, returned data, and the optional domain filter. Minor omissions like pagination or default behavior when domain is absent are acceptable given the simple tool shape and output schema.

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 description coverage is 0%, but the description adds meaningful guidance for the sole parameter: 'domain: Filter by domain (e.g. "eth_usdc")'. It goes beyond the schema's bare title/default and provides a concrete example.

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 uses a specific verb and resource: 'List the authenticated user's OWN bots eligible for a personal fund roster.' This clearly distinguishes it from sibling tools like list_bots, get_marketplace_bots, and list_open_source_bots by emphasizing ownership and fund-roster eligibility.

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?

It explains the personal-fund context and explicitly states that personal funds can never contain another user's bots, implying this is the right tool when the caller needs their own eligible bots. It does not explicitly name alternatives, but the usage context is clear.

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