Extract All Regex

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

No annotations are provided, so the description carries the full behavioral burden. It notes the target is the article's latest wikitext, but says nothing about return shape, whether results are aggregated per pattern, cost or rate limits, or how failures (e.g., missing article) are handled.

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?

A single front-loaded sentence that states the action first and supplies the pattern list as supporting detail. The parenthetical enumeration is information-dense rather than wasted, though it could be trimmed.

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?

With no output schema and no annotations, the description should explain what an agent receives back from a multi-pattern extraction. It omits return format entirely, leaving a meaningful gap for a tool whose whole value is the collection of extracted entities.

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%, so lang, date_limit, and article_name are already documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb ('apply all built-in patterns') and a precise resource ('an article's latest wikitext'), and enumerates the seven patterns it covers. This distinguishes it from a custom-regex sibling, but it does not explicitly name or contrast with extract_with_regex or extract_citations.

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 phrase 'all built-in patterns' implicitly signals bulk extraction versus the single-pattern sibling extract_with_regex, but there is no explicit statement of when to prefer this tool, when not to, or what alternatives exist for narrower needs.

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