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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, so the bar is lower; the description still contributes the page size of 50, which is nowhere in the schema (only offset is exposed). It does not say what happens at the end of the listing or whether there is a total count, so it is useful but not exhaustive.

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 clauses with zero waste, both front-loaded with the enumeration behavior first and the follow-up obligation second. Nothing is repeated from the title or annotations.

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 read-only list tool with no output schema, the description should still say what an 'identity' contains (id only, or name plus status) and how to tell the listing is exhausted. Neither is covered, so the agent knows how to page but not what it receives back.

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?

One optional parameter ('offset') has zero schema description coverage, so the description must compensate. 'In pages of 50' implicitly defines the page size and makes offset interpretable, but it is ambiguous whether offset counts pages or individual records, which is exactly the ambiguity an agent would hit first.

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 ('List owned contract identities') plus scope ('owned') and pagination size, which distinguishes it from get_quality_contract's full-record read. It stops short of naming the sibling explicitly, but 'identities' versus 'the full contract' makes the split inferable.

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 second clause gives downstream sequencing ('read the full contract before reviewing or approving it'), implying this listing is a discovery step feeding get_quality_contract / approve_quality_contract. It never states when to prefer this over a direct fetch by id, and no exclusions are given.

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