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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral limits: deterministic gating, sourced reasons, explicit unknowns, hosting conflicts, no performance scores, no account-access guarantee, no inference/purchase/setup action, and a clarification about no-new-subscription.

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 four short sentences and front-loads the core operation. The final sentence about no-new-subscription is terse but purposeful. There is little wasted wording, though the list of exclusions could be integrated more smoothly.

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 an output schema present and rich annotations, return values and safety are already covered. The description adds scope and behavioral limits, but given six parameters with 0% schema description coverage, it is not complete enough for an agent to confidently choose enum values or know when to prefer this tool over siblings.

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 carry parameter meaning. It names five of the six parameters as gates but omits language and does not explain enum values or what each gate does operationally. The budget clarification is slightly helpful but far from sufficient for six undocumented enum parameters.

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 specific operation: applying deterministic task, hosting, platform, budget, and access gates to published dossiers. This is clearer than a tautology and distinguishes the tool from sibling retrieval/comparison tools. It does not explicitly say what the output is, but the output schema covers that.

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 does not state when to use this tool versus alternatives such as botclaw_compare or botclaw_search. It lists exclusions like no performance scores or purchase action, which implies some boundaries, but gives no explicit routing or when-not-to-use guidance.

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