text_find_replace

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

No annotations are provided, so the description carries full burden. It mentions features but does not disclose whether the tool is destructive, what permissions are needed, or if it returns a new string versus modifying in place. Lacks detail on side effects or behavior beyond basic functionality.

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 two sentences, front-loading key features. However, the title is null and the structure lacks organization of parameters or return values.

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, no annotations, and an open input schema, the description is insufficient. It lists features but does not explain how to invoke them via parameters or what the tool returns. The reference to describe_tool suggests the description is intentionally incomplete.

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?

The input schema is an open object with additionalProperties true, so schema coverage is 100% but provides no structure. The description lists supported features (case-sensitive, regex, etc.) which adds meaning, but does not map these to specific parameter names or types, leaving ambiguity.

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 as a find and replace tool with specific features like case-sensitive search, regex, whole-word matching, and replace-all or first-match modes. This distinguishes it from sibling text tools that handle case conversion, diff, etc.

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 implies usage for text find/replace tasks but does not explicitly state when to use this tool versus alternatives. It directs to describe_tool for full guidance, which indicates incomplete usage instructions.

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