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

Annotations already declare readOnly/idempotent/non-destructive/non-open-world, yet the description adds meaningful context: it replays against a deterministic chart, covers exceptions and harm/review publication gates, and explicitly does not approve or publish. That clarifies the gate semantics beyond the safety 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?

Three tight sentences, front-loaded with the audience and purpose, then the replay scope, then the negative boundary. No 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?

An output schema exists so return values need not be described, and annotations carry the safety profile, but for a 10-param tool with a nested rule object and low schema coverage the description leaves parameter usage under-specified.

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?

With 10 parameters and only 30% schema description coverage, the description should explain the rule payload and chart-location inputs, but it names no parameters at all. The complex nested 'rule' object and the place-vs-coordinates anyOf are left entirely to the schema.

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 specific verbs (validates, replays) and the resource (typed rule DSL, proposed rule) and scopes to a deterministic chart. It clearly separates this from review-queue or citation siblings, though it doesn't name a specific alternative.

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?

'Reviewer/developer tool' implies the audience and 'does not approve or publish' draws one boundary, but there is no explicit when-to-use guidance or naming of alternatives like review_lal_kitab_rule or list_rule_review_queue.

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