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

No annotations are supplied, so the description carries the full burden. It does disclose the return shape, an explicit negative ('does not return the full text of entire regulations'), and that charges/authorization are governed by the OpenAny gateway, which is genuinely useful. However, it never states this is a read-only operation despite the POST-style naming, and says nothing about result ordering, relevance, or the 50-result cap beyond what the schema already documents.

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?

Four sentences, front-loaded with the core action, then filters, then return contract, then credential/billing note. Little waste; only the filter enumeration slightly duplicates the schema.

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?

For a 12-parameter tool with no output schema and no annotations, the description covers the two things an agent most needs beyond the schema: what comes back per hit and that full regulation text is not included, plus gateway credential/billing behavior. Remaining gaps are result ordering and pagination limits, which the schema's top_k partially addresses.

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% and every filter (region, authority, validity status, dates) already has an enumerated or format-documented schema description. The description's list of filter categories only restates those parameters in prose, adding no syntax, defaults, or interaction rules (e.g., how date ranges combine with keyword matching).

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 and resource with scope: searches securities-related legal provision text. The explicit note that it returns individual provisions rather than full regulations sharpens the boundary. It stops short of naming the closely related siblings (open_rh_ft_search, open_law_vector_zq_search), so the agent must infer which provision-search variant applies.

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 says the keyword parameter is required and enumerates available filters, but gives no when-to-use guidance and no exclusions. With three sibling provision-search tools (keyword, general, and vector variants), an agent has no stated basis for choosing this one over the others.

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