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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuine domain context beyond that: the binding legal authority, sequential numbering, batch release, source domain, and that page 1 is newest. It omits return format/pagination limits, but adds substantial value for a read-only list tool.

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 definition is compact and front-loads the resource identity, then adds the batch/page ordering and source. Slightly dense with the source-path annotation, but every element is relevant and there is 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?

With only one fully-documented param, no output schema, and comprehensive annotations, the description covers what an agent needs to call it correctly: resource identity, ordering, source, and what page means. It could be stronger by noting return shape or linking to the detail tool, but it is largely complete for this complexity.

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?

The single `page` parameter is fully documented in the schema (1 = newest, higher goes back), so per the coverage rule the baseline is 3. The description's 'Page 1 is the newest batch' reinforces but does not add new semantics beyond 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?

The description clearly states the resource (an index of the Supreme People's Court's Guiding Cases), what they are (binding guidance for lower courts, sequentially numbered, released in batches), and pagination order. It is specific about the resource but does not explicitly differentiate from the closely related sibling cn_guiding_case_detail, so it falls short of a 5.

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?

'Page 1 is the newest batch' implies how to consume the pagination, and the tool is implicitly for enumerating/browsing cases. However, there is no explicit 'use this when... / use cn_guiding_case_detail instead when...' routing against the most relevant sibling, leaving usage to inference.

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