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

The readOnlyHint annotation already establishes this as a safe read, so the description carries a lighter burden. It adds the underlying API endpoint and the shape of returned data, but says nothing about pagination defaults/limits in prose (the schema covers them) or result ordering. Moderate added value on top of 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?

Two tight sentences: the first defines scope and returned fields, the second states the use case, with the API endpoint appended as reference. Nothing is redundant and the key information is front-loaded.

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 a complete input schema and a readOnly annotation, the description supplies purpose, returned fields, and motivation. Enumerating the returned fields compensates for the absent output schema, leaving no material gap for correct invocation.

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 page, limit, and project_id are already fully documented in the schema, including defaults and the max-100 limit. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 a project's tracked deploys') and enumerates the returned fields (environment, deployer, repository, revision, version). This cleanly distinguishes it from the sibling airbrake_get_deploy, which fetches a single deploy.

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?

Gives a clear use context ('correlate new errors with a release'), which tells the agent when this tool is appropriate. It stops short of naming alternatives or exclusions — e.g., that airbrake_get_deploy is for a single known deploy — so it is not full when/when-not guidance.

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