init

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns rules for enabling triggers and that the host should append them to a file, which gives some behavioral context (output format and intended action). However, it lacks details on permissions needed, whether it modifies files directly, error handling, or rate limits. For a tool with no annotations, this is minimal but not entirely absent.

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 sentences that are front-loaded with the core purpose and output, followed by the intended action. Every sentence earns its place: the first explains what the tool does and returns, the second specifies how to use the output. There's no wasted verbiage or redundancy.

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 no annotations, no output schema, and a simple input schema, the description provides basic completeness by stating the tool's purpose and output usage. However, for a tool that likely involves file system operations or configuration changes, it lacks details on side effects, error conditions, or return values beyond 'CLAUDE.md rules.' This is adequate but leaves gaps in understanding the full context.

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 input schema has 1 parameter with 100% description coverage, so the schema already documents 'project_path' well. The description doesn't add any parameter-specific information beyond what's in the schema, but with high coverage and only one parameter, the baseline is strong. Since there are no parameters mentioned in the description, it doesn't compensate but also doesn't detract, fitting the baseline for this case.

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 tool's purpose: 'Initialize Callout in a project' and specifies what it returns ('CLAUDE.md rules that enable automatic review/coach/recommend triggers'). It distinguishes from siblings like 'callout_help' or 'review' by focusing on initialization rather than execution of those functions. However, it doesn't explicitly contrast with all siblings, so it's not a perfect 5.

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 implies usage context by stating 'The host should append these rules to the project's CLAUDE.md file,' suggesting this tool is for setup/configuration rather than runtime operations. However, it doesn't provide explicit guidance on when to use this vs. alternatives like 'callout_help' or 'set_target_user,' nor does it specify prerequisites or exclusions. Usage is implied but not clearly articulated.

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