run_bot_surface_diagnostic

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

With no annotations, the description carries the full burden of disclosing side effects, safety, and behavior. It only reveals that the tool runs a script, offering minimal transparency about what 'bot surface diagnostics' entails, what the script does, or what happens during execution.

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 a single, compact sentence with no redundancy or filler. It is front-loaded with the core action and resource, though it could arguably be considered under-specification rather than conciseness given the tool's complexity.

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?

Given the tool's complexity (9 params, no schema descriptions, no annotations), the description is far too sparse to enable correct invocation. It does not explain the tool's end-to-end behavior, parameter roles, or use cases, making it incomplete for an agent to confidently select and use.

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 schema description coverage is 0%, and the description provides no parameter information whatsoever. With 9 parameters all undocumented, the description fails to compensate for the schema's lack of semantic detail, leaving the agent unable to understand parameter purpose or expected 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 clearly states the action ('Run') and the resource ('script-level bot surface diagnostics'), with a reference to the specific script (scripts/bot_check.py). It is specific enough to distinguish from sibling diagnostics like run_challenge_diagnostic, but 'bot surface' remains somewhat jargon-heavy and could be elaborated for full clarity.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, expected conditions, or why one would choose this over the other diagnostic tools. The description provides no usage context.

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