edit_section

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

Annotations are absent, so description must bear full burden. Describes what it does (clear+replace) and modes, but lacks disclosure of side effects, destructiveness, or authorization requirements beyond the obvious.

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?

Description is concise and front-loaded with purpose. Uses clear bullet-like Args format without extraneous words. Every sentence adds value.

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 5 parameters, 3 required, no output schema, description covers core purpose, parameter details, and sibling differentiation. Lacks some details like return behavior and error handling, but sufficient for most use cases.

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 has 0% coverage; description compensates with detailed explanations for all 5 parameters: tracks JSON structure, start/end time units, mode options, trim_item usage. Adds significant meaning beyond schema.

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?

Description clearly states verb 'Clear+replace' and resource 'notes/CCs in a time range'. Distinguishes from sibling 'rewrite_cc' by specifying its use case for CC-only fixes.

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?

Explicitly tells when to use this tool vs alternatives: 'For CC-only fixes, use rewrite_cc instead.' Provides clear context for different modes and parameters.

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