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

Adds real value beyond the annotations: it discloses that jurisdiction guidance not tagged to the named forum is split out into a separate `profession_guidance` field and must also be read. That is non-obvious output behavior not present in the schema, and it does not contradict the readOnly/idempotent hints.

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 sentences, no filler, with the core retrieval behavior front-loaded. The second sentence is slightly tangled ('returned apart, in `profession_guidance`') but still parses cleanly.

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, the description covers the key result quirk (the separate `profession_guidance` bucket) that an agent would otherwise miss. It does not describe the shape of the matched instruments themselves, but the important completeness gap is addressed.

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 the schema already documents `task`, `forum` and `jurisdiction` including the enum values and the omit-to-be-asked behavior. The description reinforces only the `forum` semantics (out-of-forum guidance routing) and adds nothing about `task` phrasing.

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: returns stored court/tribunal AI instruments matching a task and forum via a named rule matcher. An agent can tell it retrieves rule instruments, not guidance documents or precedents, though it never names the sibling tools (get_jurisdiction_guidance, search_library) it contrasts with.

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?

Implies usage through the task+forum framing and the note that forum-less calls prompt the user, but gives no explicit when-to-use/when-not or which sibling to pick instead (e.g., when to use get_jurisdiction_guidance versus this).

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