deployado_list_deployments

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description's only extra contribution is noting the returned fields (status, version, timing), which is modest but genuine value; it says nothing about ordering, pagination, or empty results.

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?

A single short sentence with zero filler, and the scope ('for an app') and output fields are front-loaded. It could have used one more clause for sibling differentiation without becoming bloated, but there is no waste as written.

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?

This is a simple two-parameter read-only list operation with full schema coverage, complete annotations, and no output schema requirement. The description plus structured fields give an agent everything needed to select and invoke it correctly.

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 coverage is 100%: app_id (UUID) and limit (default 10, max 50) are both fully documented in the schema. The description adds nothing about limit behavior or result ordering/capping, so the baseline of 3 applies.

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 ('List') and resource ('deployments') with the scope narrowed to a single app, and names the fields surfaced (status, version, timing). It is clear on its own, but it does not explicitly distinguish itself from close siblings like deployado_get_deployment or deployado_current_deployment.

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 word 'recent' and the required app_id imply the intended use case (browse a history for one app), but the description never states when to prefer this over get_deployment, current_deployment, or list_releases. No exclusions or prerequisites are given; usage must be inferred from the sibling name pattern.

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