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

With no annotations present, the description carries the full burden and does a decent job: it discloses that results are paginated at 30 per page by default, that the caller's OpenAny gateway credentials are used, and that billing and authorization are gateway-determined. Those are exactly the behavioral facts an agent needs before spending a call. It does not say whether returned records are current versus historical, which is the main remaining 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?

Four short sentences, front-loaded with what is retrieved and keyed on, then pagination, then credential/billing context. Nothing is padded or repeated. Slightly more compression is possible in the gateway sentence, which is why it is not a 5.

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, three-parameter lookup with no output schema and no annotations, the description covers the essentials: what is returned, how it is keyed, how it is paginated, and who pays/authorizes. It would be fully complete if it indicated whether these are in-force or historical freezes and gave a hint of the record fields.

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 would be 3, but the description adds real meaning: it frames id and tyshxydm as interchangeable lookup keys for the same entity, and it supplies a page-size fact (30 records per page) that the schema's pageNo entry ('Page number; defaults to 1') does not contain. That extra context justifies going above the baseline.

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 names a specific verb and resource: 'Retrieve equity freeze records for an enterprise', plus the two accepted entity keys. This is distinguishable from same-family siblings such as enterprisepledge or enterpriseexecutions because the resource noun differs. It stops short of explicitly contrasting with those siblings, so an agent still has to infer the boundary.

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?

Usage is only implied: an agent can infer it should call this when it needs a company's equity freeze records. There is no explicit statement of when to use this versus adjacent tools (equity pledge, executions, or the qcc equity-freeze endpoints), and no exclusions or prerequisites beyond needing an enterprise identifier. The one genuine usage hint is that either an enterprise ID or a USCC will do.

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