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

readOnlyHint=true already establishes the safety profile, so the description's only added content is the raw v2 endpoint path. It says nothing about ordering, result limits, pagination behavior beyond the schema, auth/permission requirements, or rate limits — exactly the context an agent would need.

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 sentences, front-loaded with the action and scope. The endpoint string is arguably filler for an LLM agent, but it is compact and not confusing.

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?

With no output schema, the description carries the burden of describing what a 'deployment history' entry contains and how to page through it; it does neither. No mention of ordering, default page size, or how results relate to the per-deployment siblings.

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%, including explicit notes that page_size maps to page[size] and page_cursor to page[cursor], so the schema carries the parameter semantics. The description adds no format or constraint detail beyond that, making the baseline 3 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+resource ('List a site's deployment history') and scopes it to a site, which is more precise than the title alone. It does not distinguish itself from close siblings like forge_get_deployment, forge_get_deployment_status, or forge_get_deployment_log, so an agent must infer the list-vs-single split.

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?

There is no when-to-use guidance and no mention of alternatives. The description never tells the agent to use this for enumerating deployments versus forge_get_deployment for fetching a specific one, nor does it mention prerequisites like needing a valid site/server.

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