replace

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Replace' implies a mutation operation, but the description doesn't clarify if this is destructive (overwrites original), requires specific permissions, has side effects, or what the expected outcome is. It lacks details on error handling, performance, or what 'pattern section' means in practice.

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 extremely concise with just two words, 'Replace pattern section', which is front-loaded and wastes no space. Every word contributes directly to the tool's purpose, making it efficient despite potential under-specification.

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 the complexity implied by sibling tools (e.g., pattern manipulation in a musical context), no annotations, no output schema, and vague purpose, the description is incomplete. It doesn't explain what a 'pattern section' is, the tool's behavior, or return values, leaving significant gaps for an AI agent to understand and invoke it correctly.

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%, with clear parameter descriptions ('Text to replace' and 'Replacement text'). The description adds no additional semantic context beyond the schema, such as examples, constraints, or how parameters interact with 'pattern sections'. Since the schema is well-documented, a baseline score of 3 is appropriate.

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 'Replace pattern section' indicates the tool performs a replacement operation on pattern sections, which is a clear verb+resource combination. However, it doesn't specify what constitutes a 'pattern section' or differentiate this tool from other pattern manipulation siblings like 'transpose', 'reverse', or 'humanize', leaving the scope somewhat vague.

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 no guidance on when to use this tool versus alternatives. With many sibling tools for pattern manipulation (e.g., 'transpose', 'reverse', 'humanize', 'quantize'), there's no indication of whether this is for text replacement in patterns, musical element substitution, or other contexts, nor any prerequisites or exclusions mentioned.

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