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

With no annotations, the description carries the full burden, and it does disclose three useful traits: results are paginated at 30 per page by default, credentials come from the caller's OpenAny gateway, and billing/authorization are handled at the gateway rather than by this tool. It does not state the read-only nature explicitly, what the response contains, or what happens when neither identifier is supplied.

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 short sentences: what it returns and by what key, then pagination, then credential/billing behavior. Front-loaded and free of filler; every sentence carries information the structured fields do not.

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 read-only lookup with a fully described three-parameter schema and no output schema, the definition is serviceable. However, with 0 required parameters an agent could invoke it with no arguments at all, and the description gives no indication of whether that is valid, nor of error behavior or what a debtor record contains.

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, and the description adds real meaning by presenting id and tyshxydm as alternative lookup keys ('using its enterprise ID or unified social credit code') – the schema alone never says the two are substitutes. It still leaves the 'no required parameters' case unaddressed, i.e. whether either key is actually mandatory.

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 states a specific verb and resource: 'Retrieve dishonest judgment debtor records for an enterprise'. That phrasing implicitly separates it from the sibling yuandian_get_open_rh_enterpriseexecutedperson (enforcement/executed person records), which is the main confusion risk given the similarly named tool key. It stops short of explicitly naming that sibling, so an agent must infer the boundary rather than read it.

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?

There is no when-to-use guidance, no exclusions, and no mention of the closely related enterpriseexecutedperson or risk-scan tools in the crowded yuandian/qcc sibling set. The only selection-like information is which identifiers are accepted, which is about how to call it, not whether to call it.

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