intelligent_law_search

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

Discloses semantic search behavior and domain selection via search parameter. No annotations provided, but description covers primary behavioral traits for a non-destructive search tool. Lacks mention of rate limits or result set metadata.

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?

Concise, front-loaded with purpose, uses bullet-point clarity. Every sentence adds useful context without 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?

Explains overall workflow (search then retrieve full text). Does not describe pagination parameters (display, page) in description, but schema covers them adequately. No output schema, but return format is implied.

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?

Adds value beyond schema by explaining search parameter domain options and giving natural language query examples. Schema already provides good descriptions for all parameters.

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?

Clearly states it's an intelligent semantic search on clause text, distinguishes from sibling search_law that only matches law names. Provides example keywords and target agency.

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 contrasts with search_law (law name matching) and recommends get_law_text(mst) for full text retrieval after searching. Gives clear when-to-use guidance.

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