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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one meaningful trait – that this only triggers creation + deploy and does not wait for readiness – but omits auth/permission requirements, side effects, and what state is left behind after the call.

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?

Two front-loaded sentences with no filler; the scope qualifier and the sibling routing are both stated in minimal space. The parenthetical is terse but effective rather than wasteful.

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 mutation tool with no annotations and no output schema, the description is thin: no auth needs, no description of the resulting environment or how to observe its status, and the lone parameter is undocumented. An agent has enough to route but not enough to call it confidently.

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 single parameter branchName has 0% schema description coverage, so the description must compensate and does not. It never states the format (branch ref? name?), whether it defaults when omitted (it is not required), or how it maps to the created environment.

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 (Create) and resource (BunnyShell ephemeral environment), and the parenthetical '(create + deploy trigger only)' scopes exactly what the operation does. It explicitly distinguishes itself from the sibling provision-ephemeral-environment-and-wait, so an agent can route correctly without opening the schema.

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?

Names the alternative tool and the condition that selects it ('Prefer provision-ephemeral-environment-and-wait for normal flows'), implying this one is for flows where waiting is not wanted. Clear routing context, though it never states explicitly when this tool IS the right choice.

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