List app deployments

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

No annotations are provided, so the description must carry this burden. It only states pagination with skip/take, which is already apparent from the schema. It does not disclose ordering, response format, default behavior, or any edge cases, offering little beyond what is structurally known.

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 fluff. Every word adds value: it states the action, the scope, and the key feature (pagination).

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 paginated list, the description is minimally adequate, but without an output schema or annotations, it leaves gaps about what data is returned (e.g., fields, ordering, whether canceled deployments are included). It does not clarify differences from listDeployments.

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 0%, so the description adds meaning by clarifying that skip/take are pagination parameters and that uuid identifies the application. It compensates partially for the missing schema descriptions, though it could define ranges or semantics further.

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?

The description clearly states a specific verb ('List') and resource ('deployments for an application'), and explicitly mentions pagination. It distinguishes this tool from broader siblings like listDeployments by scoping to a single application via uuid.

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 description implies usage (when you need deployments for a specific app), but does not explicitly mention alternatives or when not to use it. With sibling tools like listDeployments and getDeployment present, but no guidance is provided.

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