boot_instructions

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

With no annotations provided, the description carries the full burden. It transparently states the tool 'does not edit client files' and 'returns the rule text to install,' preventing expectations of side effects. It doesn't discuss permissions or error conditions, but for a text-generation tool this is adequate disclosure, meriting a 4.

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?

Three sentences with zero redundancy: purpose, usage context, and a side-effect disclaimer. Every sentence earns its place, making the description compact and highly scannable.

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 simplicity (2 params, no annotations, no output schema), the description covers all essentials: what it generates, when to use it, and what it returns. The statement 'returns the rule text to install' substitutes for an output schema, and the integration with 'initialize' places it in a complete workflow.

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 references namespace in an example but adds no new semantic meaning beyond the schema's own descriptions. The 'target' parameter is already described in the schema as controlling 'recommended filename/location only,' so the description adds no incremental value.

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 it 'Generate copy-paste startup instructions' for a client/global/project rule, using a specific verb and resource. It distinguishes from siblings by explicitly noting it 'does not edit client files; it returns the rule text to install,' which separates it from create/update/delete tools.

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 gives explicit context: 'Use this after initialize' and explains the purpose ('future new sessions automatically call initialize...'). It does not explicitly name alternatives or when-not-to-use, but the workflow context is clear and excludes file-editing use cases, which earns a 4.

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