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

With no annotations provided, the description carries the full burden. It states the tool is a write-tier action requiring approval, implying destructive behavior. However, it does not disclose whether the action is reversible, what the response is, or any side effects beyond 'start fresh'.

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 concise with three sentences: purpose, usage triggers, and approval note. It is front-loaded and every sentence adds value. No redundancy or unnecessary text.

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 output schema and no annotations, the description covers purpose, usage triggers, and permission requirements. It does not explain return values or how to verify the reset, but for a straightforward destructive action, the context is largely complete. Missing mention of using list_pipeline_learnings to check before resetting is a minor gap.

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 does not add significant meaning beyond what the schema already provides for parameters. It restates pipeline_id and mentions output_format behavior ('clears all formats if not specified'), but this is already in the schema description.

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: 'Reset all learnings for a pipeline and start fresh.' The verb-resource pair is specific. Example user phrases distinguish it from siblings like 'list_pipeline_learnings' or 'update_pipeline_style_guide'.

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 explicitly lists when to use the tool (e.g., when user says 'forget what you learned') and includes a note about write-tier approval. However, it does not provide when-not-to-use guidance or mention alternative tools like 'list_pipeline_learnings' before resetting.

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