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

No annotations are provided, so the description carries the load, and it does disclose a non-obvious behavioral trait: every bot carries a "fieldable_in" list and mismatched bots are rejected downstream by add_bot_to_fund. It also hints at payload content (stats, capacity, crowd signals). It does not mention read-only semantics, pagination, or result-set size limits, which matters for a browse-all endpoint.

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?

Front-loaded with purpose and scope, then the fund-type gating rule, then a compact Args block. Every sentence carries information; the parenthetical examples add precision rather than padding. The line breaks are cosmetic and do not hurt scanability.

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?

Two optional params, both explained, and an output schema exists so return values need not be spelled out. The fund-type gating behavior — the one thing that could cause a downstream failure — is covered. Missing only the fund_type default and any notion of result volume for an "ALL bots" listing.

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, and it does: domain is explained with a concrete example ("eth_usdc") and fund_type is documented with its three permitted values. What it omits is the default behavior — the schema defaults fund_type to "standard" — so an agent reading only the description would not know the unfiltered default.

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 and resource ("Browse ALL bots fieldable in funds") and enumerates the subcategories it covers — platform bots, your own bots, open-sourced bots, directional building blocks — which implicitly distinguishes it from list_my_bots, list_open_source_bots, and list_directional_bots. The "same marketplace human managers see in the fund editor" framing pins down exactly which dataset this is.

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?

Gives clear workflow context: filter by the fund type you intend to add to, because a bot not listed for that fund type will be rejected by add_bot_to_fund. That tells the agent when to use this tool (pre-selection for fund composition). It stops short of naming alternatives or exclusions, notably the near-duplicate sibling get_marketplace_bots, which the agent must disambiguate on its own.

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