install_method_spec

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the non-destructive nature of dry_run, the paid-account requirement, and the Free tier step cap. It does not explicitly state what the tool returns on success or how it handles conflicts beyond parameter hints, but it provides meaningful context beyond minimal descriptions.

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 four sentences long, with the purpose front-loaded in the first sentence. Every sentence provides useful information (e.g., method_md input, dry_run preview, account constraints) with no redundancy or fluff.

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?

The tool has 7 parameters and no output schema, so the description should ideally explain return values or fallback behavior. It provides useful operational context (dry_run, account limits) but does not mention what is returned on success/failure or what happens when an existing template is overwritten. This is an adequate but incomplete contextual picture.

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 description coverage is 100%, so the baseline is 3. The description repeats some param details (method_md content, dry_run behavior) that are already present in the schema without adding new meaning. It does not explain parameters in a way that materially enhances the schema's clarity.

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 ('Install') and clearly identifies the resource ('OFL method spec') and the resulting artifact ('runnable Harmonica chain template'). It is easily distinguished from the session/project-oriented sibling tools, which are unrelated in purpose.

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 provides clear context for when to use the tool (installing a method spec) and includes important operational guidance: using dry_run to preview without writing, and noting the paid-account requirement with a free tier cap of 3 steps. It does not explicitly name alternatives or exclusion scenarios, but no obvious alternative exists among the sibling tools.

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