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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful return-content context by listing totals, dates, notice period, status, and lifecycle stage, though it does not discuss pagination behavior or authentication requirements.

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 a single front-loaded sentence with no wasted words. The parenthetical definition, example use case, and endpoint all contribute directly to understanding the tool.

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 9-parameter filtered list tool with no output schema, the description gives enough return-field and usage context for an agent to understand the tool. It leaves pagination and rate-limit behavior implicit, but those are partially covered by the schema's cursor and limit parameters.

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?

The schema has 100% description coverage for all 9 optional parameters, including sort, limit, cursor, stage, status, company, location, and modified_since. The description adds no parameter syntax or filtering guidance beyond what the schema already provides, so the baseline of 3 is appropriate.

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 contracts') and immediately defines what a contract is ('agreements for plans and resources'), which separates it from sibling list tools such as memberships. It also names the data dimensions returned and the underlying OfficeRnD endpoint.

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?

Provides a clear usage example: 'find contracts up for renewal or serving notice.' This gives concrete context for when the tool is useful, though it does not name alternative tools or state when not to use it.

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