cases_search_by_article

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

No annotations provided; description mentions it returns cases with context snippets but lacks details on read-only nature, auth needs, or rate limits.

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 efficient sentences: first defines purpose with examples, second describes return value. No wasted 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?

Adequately covers basic functionality for a search tool with 4 params, but lacks details on interpretation enum and pagination behavior that would be helpful.

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%; description adds value by giving examples for the 'article' parameter but does not clarify 'broad' vs 'narrow' interpretation or pagination beyond schema.

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 searches for cases mentioning a specific legal article, provides examples (e.g., '6:162 BW'), and distinguishes from sibling tools like 'cases_search' which is broader.

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 when an article reference is available but does not explicitly state when not to use or compare with alternatives like 'cases_search'.

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