regex_regex_findall

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

Describes output format and group behavior; no annotations to contradict. Does not mention error handling or flags behavior, but for a read-only regex tool, it's mostly transparent.

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?

Two sentences with three clear parts: purpose, group behavior, alternative. Front-loaded and no extraneous words.

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?

Covers basic use and differentiation from sibling; lacks explanation of flags parameter and error scenarios. Given output schema exists, return values are partially covered.

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% description coverage; description only implies pattern and text roles and mentions groups. No details on flags parameter or accepted formats, 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?

Description clearly states it returns non-overlapping matches as a list, specifies group behavior, and distinguishes from sibling regex_findall_with_positions. Verb: 'Return', resource: 'matches', scope: 'all non-overlapping'.

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 provides alternative ('use regex_findall_with_positions for positions') and characterizes tool as 'Simple and fast'. Does not state when not to use, but the contrast is clear.

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