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

With no annotations, the description carries the burden and does so well: it discloses pagination defaults, that items are summaries rather than full documents, and that credentials/charges/authorization flow through the caller's OpenAny gateway. It leaves open whether a total-record count is returned and whether page size can be adjusted, which is the main residual gap.

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 paragraphs, front-loaded with the resource and identifier constraint, then response shape, then auth/cost. Minor redundancy: the pageNo default of 1 is restated from the schema, and the per-page default of 30 has no corresponding parameter.

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 tool is a simple 3-parameter read with no output schema, and the description covers the pieces an agent needs: how to identify the enterprise, what the response envelope looks like, that items are summaries, pagination defaults, and the credential/billing model. Nothing material for correct invocation 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 coverage is 100%, so the baseline is 3; the description earns above that by stating an actual requirement ('at least one of id and tyshxydm') that the schema does not encode, since the schema lists zero required parameters. It adds no format guidance for the credit code beyond what the schema property description gives.

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 verb and resource ('Retrieve a paginated list of litigation documents related to an enterprise') plus the two accepted identifiers, and explicitly contrasts the output with full-text retrieval, which separates it from the case/document detail siblings. An agent can distinguish this from yuandian_get_open_rh_enterprisewritagg and the case-details tools without opening a schema.

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?

Gives an explicit selection constraint ('provide at least one of id and tyshxydm') and routes the agent onward for full text ('use the document information to call a case or document details API'). It lacks any when-not guidance (e.g., when the aggregation sibling or company-detail call is preferable), so it falls short of a full 5.

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