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

Beyond the annotations, the description discloses meaningful behavior: 'this_bot' adds skills, rules and paused routines without replacing the Bot's role, while 'new_bot' returns a setup prompt. This clarifies the write-like effect and different return modes. It does not detail what 'this_bot' returns or whether the operation is idempotent, but it adds substantial context beyond the readOnlyHint=false annotation.

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 two tight sentences, front-loaded with the core action and then the target-specific behavior. Every clause carries useful information with no filler.

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 two-parameter tool with no output schema, the description covers the key behavior of both target modes and avoids replacing the current Bot's role. It omits what 'this_bot' returns and any permission or idempotency details, which are minor but real gaps.

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 coverage is 100%, so the baseline is 3. The description adds real meaning for the 'target' parameter by explaining the default and the distinct effects of 'this_bot' versus 'new_bot'. The 'slug' parameter is left to the schema, which already says it comes from search_templates.

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 uses a specific verb and resource: 'Get step-by-step install instructions for one template.' It also distinguishes the two installation targets. It does not explicitly name install_bundle as the alternative for multi-template installs, so sibling differentiation is implied rather than explicit.

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 clearly explains the two usage modes: 'this_bot' for adding skills/rules/routines to the current Bot, and 'new_bot' for returning a setup prompt. It does not state when to choose this tool over install_bundle or search_templates, so the guidance is clear but lacks explicit alternatives.

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