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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety behavior is fully covered structurally. The description adds real substance by listing the actual rule contents, but says nothing about the return format (a markdown block? a string? with placeholders?) or whether the output is meant to be pasted verbatim.

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?

One sentence, front-loaded with the resource identity followed by a compact colon-list of the rules. Every clause is readable and none is filler, though the enumerated rule contents are arguably a preview of the payload rather than selection-critical information.

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 zero-parameter, read-only content tool with no output schema, the description covers what the block contains and where it belongs. The one remaining gap is the shape of the returned content, which the absent output schema would otherwise need to cover.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a parameterless, take-it-as-is tool.

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 names the resource precisely: a safety and memory rules block for a business CLAUDE.md, and enumerates the rule categories it covers. It is distinguishable from siblings like daily_routine or voice_guide_template by its subject matter, though it never states the action (returns text? renders a block?) and leaves the agent to infer that the tool supplies content rather than writing it.

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?

Usage is implied by the phrase 'for a business CLAUDE.md', so an agent can infer this is used when assembling that file. There is no explicit when-to-use, no exclusion, and no comparison to the sibling templates (daily_routine, scaffold_business_os, voice_guide_template), so the agent must reason about ordering itself.

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