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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, and idempotentHint=false. The description adds the registry constraint but conspicuously leaves the tension between 'Run a producer' and readOnlyHint unexplained, and says nothing about why idempotentHint is false or what a failed run looks like. It adds only marginal context over the annotations.

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 short sentences with no filler and the key constraint placed last. It is not bloated, but the density of undefined jargon means the brevity comes at the cost of comprehension rather than from efficiency.

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 tool with a nested request object, no output schema, and 0% parameter documentation, the description is far too thin. It never defines 'producer', 'producerControl/0.2', or 'Lens', nor does it explain what the request must contain or what the caller receives, leaving an agent unable to invoke it correctly.

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% with two required parameters, one of which ('request') is a nested object that is entirely undocumented. The description adds a little meaning to 'producer' (must come from the shipped registry) but gives no insight into the structure or contents of 'request', so it fails to compensate for the coverage gap.

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 names an action ('Run a registered producer') and an output ('producerControl/0.2'), but both are opaque domain jargon that a fresh agent cannot decode. It never states in plain terms what the tool actually does, and it does not differentiate itself from siblings like law_prepare_answer, law_publish_answer, or law_answer_capabilities beyond implying a 'later verifiable preparation' step.

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 guidance is a constraint ('The producer is chosen only from the shipped registry'), which says what inputs are legal, not when to pick this tool over the many siblings. No when-to-use, no when-not-to-use, and no named alternatives are offered.

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