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

With no annotations, the description carries the full behavioral burden. It usefully discloses pagination at 30 records per page by default, that gateway credentials are used, and that charges and authorization are gateway-controlled, but it does not explain failure behavior or the practical requirement that at least one enterprise identifier be 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?

The description is three tight sentences, front-loaded with the operation and resource. The pagination and gateway-credential details are relevant and no wording is wasted.

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 simple paginated read endpoint with no output schema, the description covers the core operation, pagination, and auth/billing context. However, because all three parameters are optional in the schema, it should more clearly explain that an enterprise identifier is required in practice and how the two identifier fields relate.

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 description coverage is 100%, so the baseline is 3. The description adds that either an enterprise ID or a unified social credit code can identify the enterprise and mentions the default page size, but it does not clarify mutual exclusivity or requiredness of the otherwise all-optional 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?

The description states a specific verb and resource: retrieve equity pledge records for an enterprise. This clearly distinguishes the tool from other enterprise-risk endpoints such as frozen equity or guaranty, though it does not explicitly name sibling alternatives.

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?

It says the tool is used with an enterprise ID or unified social credit code, but gives no explicit guidance on when to choose this tool versus related enterprise record endpoints. It also does not say whether one identifier is required, whether both may be supplied, or which identifier is preferred.

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