correct_solution

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

The description discloses that it replaces all occurrences of `find` with `replace` in the solution text. With no annotations, it sufficiently covers core behavior, though it could mention whether modifications are in-place or require re-saving.

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, front-loaded with purpose, followed by usage guidance and sibling differentiation. Every sentence adds value with no 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 full input schema coverage and an existing output schema, the description covers purpose, behavior, usage, and parameter sources comprehensively for a simple find-and-replace tool.

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 coverage is 100%, so baseline is 3. The description adds context for entry_id (which previous calls provide it) and clarifies that find is exact text, enhancing understanding beyond schema definitions.

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 fixes specific text in an already-saved solution, distinct from enrichment. It uses a specific verb ('correct') and resource ('solution text'), effectively distinguishing it from siblings like enrich_solution.

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 explicit guidance on when to call the tool (user corrects a name, term, or detail saved incorrectly) and when not to (use enrich_solution for new context). Includes an example for clarity.

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