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

With no annotations, the description carries the full disclosure burden, and it does deliver one genuinely non-obvious behavioral fact: an empty list signals corpus absence rather than an error — important for agent branching. Beyond that it says nothing about ranking of results, what "verified" concretely guarantees, corpus scope, or any rate/permission constraints.

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?

Three short sentences with no filler, and the empty-result semantics are stated up front where an agent will read them. The only waste is the 'Legal Oracle:' label, which occupies prime opening position without adding information.

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?

Because an output schema exists, the description is not obligated to explain return structure, and it correctly covers the one edge case an output schema cannot express (empty list meaning). However, for a three-parameter retrieval tool with zero schema documentation and no annotations, the missing limit semantics and undefined notion of 'verified' leave real gaps.

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 0%, so all three parameters are bare in the schema, and the description only partially compensates: it clarifies that jurisdiction is optional and acts as a filter. The required query parameter is only implied, and the limit parameter and its default of 5 are never mentioned, leaving an agent to guess truncation behavior.

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?

"Which verified provisions relate to a query" states the resource (verified legal provisions) and the operation (retrieval by query relevance) clearly enough that an agent can distinguish it from a citation-verification sibling. The 'Legal Oracle:' branding prefix is noise, and it never explicitly contrasts itself with verify_citation or legal_breakdown, so it stops short of a 5.

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 only usage-adjacent content is "Optional jurisdiction filter," which describes a parameter default rather than when to call this tool. There is no guidance on when to prefer it over legal_breakdown or verify_citation, no prerequisite steps, and no exclusions.

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