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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds genuine behavioral value by disclosing the inclusion/exclusion filter (publication-gated only; drafts and open contradictions omitted), but says nothing about ordering, pagination, or what 'publication-gated' operationally means.

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 tight sentences with the scoping constraint front-loaded and no wasted text. Efficient, though extremely terse for a five-parameter search tool.

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?

The presence of an output schema means return values need not be explained, and annotations carry the safety profile. Still, for a 5-param search tool with 0% schema coverage, the description omits all parameter guidance and explicit usage routing, leaving gaps an agent must guess at.

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?

Five parameters (limit, query, topic, harmClass, tradition) have 0% schema description coverage, and the description mentions none of them or their semantics. With low coverage the description must compensate, but it adds no filtering syntax, value guidance, or interaction between parameters.

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 resource (publication-gated rules and rights-safe source metadata) with an explicit scope limitation, and the exclusion of drafts/open contradictions distinguishes it from list_rule_review_queue. However, the verb is only implied via 'Returns' rather than a clear search action, and no sibling is named directly.

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?

Usage is only implied: by excluding drafts and open contradictions, it hints that list_rule_review_queue is the tool for those cases, but no explicit when-to-use or alternative is stated. The agent must infer routing from the exclusion clause.

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