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

With no annotations provided, the description carries the full burden and does deliver real behavioral context: API key required, no credit consumption, and a 60/day rate limit. It also clarifies that the full set (60+) is returned rather than a filtered subset. It stops short of stating what happens on a missing/invalid key or whether pagination exists.

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?

The operational constraints are front-loaded in a bracketed tag, and the core purpose follows immediately. The bilingual restatement doubles the length, but it is deliberate audience coverage and no sentence is filler.

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 simple no-argument listing tool with no output schema and no annotations, the definition covers the essentials: auth requirement, cost, quota, and what fields come back (names and specialties). Only edge-case behavior (invalid key, empty results) is missing.

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 the single optional client_tag parameter is thoroughly documented in the schema (format, logging-only behavior, non-rejection). The description adds nothing about parameters, which is acceptable given the schema does the work, so the baseline 3 applies.

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 states a specific verb+resource: returning a list of 60+ specialist legal leaders with their names and specialties. It is clearly distinguishable from chat_leader or ask_expert by being a read-only directory listing, though it never names those siblings. Purpose is unambiguous on its own.

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?

It discloses prerequisites and constraints ('KEY REQUIRED', 'no credits, 60/day'), which implies this is a metered listing call. However, it gives no guidance on when to prefer this over sibling tools like chat_leader or find_village_lawyer, so usage is only implied.

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