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

The annotations already declare this as a read-only, idempotent, non-open-world operation. The description adds a meaningful behavioral prerequisite: access requires an Enterprise Data key passed via the X-API-Key header, with a documentation link. It does not discuss pagination behavior or error cases, but the auth disclosure is valuable beyond the annotations.

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 two tight sentences. The purpose is front-loaded, and the authentication requirement follows without wasted prose.

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 list tool with complete schema documentation and clear annotations, the description is largely complete: it states scope, key return fields, and an auth prerequisite. It could explicitly mention pagination or how results are ordered, but the schema already exposes the page parameter.

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 all five parameters are already documented in the input schema. The description adds scope context around a line of business and the returned fields, but it does not clarify parameter semantics beyond what the schema provides.

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 and scope: all contract rows for one line of business, including contact, end dates, and amounts. It is specific enough to understand the operation, but it does not differentiate itself from close siblings such as assay_supplier_contracts or assay_contract.

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?

The description does not say when to use this tool versus alternatives such as assay_contract, assay_line, or assay_supplier_contracts. It only states an authentication prerequisite, leaving the agent to infer the selection context from the sibling names.

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