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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal what the tool returns ('a JSON array of bot entries with gamified card ratings') and describes the data as 'normalized stats and capacity info.' However, it does not explicitly state that this is a read-only/research-only operation or disclose any limitations beyond the personal-funds note.

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 compact and front-loads the core purpose in the first sentence. The NOTE, args section, and return-type mention all serve useful purposes. Minor redundancy exists between 'Browse open-source bots' and 'This tool is for researching the broader bot ecosystem,' but the overall structure is efficient.

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 simple tool with one optional parameter and an output schema, the description covers the key facts: what the tool does, how the param works, and what the response looks like. The main gap is the lack of guidance differentiating it from get_marketplace_bots, but the description is otherwise sufficient for an agent to call it correctly.

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%, so the description must compensate for the undocumented 'domain' parameter. It does so adequately by explaining 'Filter by domain' and providing a concrete example, 'eth_usdc.' This meaningfully adds value beyond the bare schema, though it does not enumerate possible domain values.

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 states a clear verb and resource: 'Browse open-source bots with normalized stats and capacity info.' It also adds context with 'This tool is for researching the broader bot ecosystem,' which helps define its role. However, it does not explicitly differentiate it from the similarly named sibling get_marketplace_bots, so it stops short of a 5.

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?

The description gives explicit usage context with the NOTE, explaining that personal funds only contain the authenticated user's own bots and directing agents to list_my_bots for roster-eligible strategies. It also states that this tool is for ecosystem research. It does not mention when to prefer closely related alternatives like get_marketplace_bots, but the guidance provided is clear and specific.

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