iaas_get_deployments

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety behavior is covered. The description adds only the raw REST path (GET /iaas/api/deployments), and says nothing about default page size, whether results are unpaginated by default, or what identifying fields a deployment record carries.

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?

It is short, but the first two lines are redundant ("Get Deployments" / "Get all deployments"), and no line is front-loaded with the information an agent would actually need, such as pagination defaults or scope.

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 parameterless-required read-only list endpoint with full schema coverage, an annotations safety profile, and no output schema, the definition is just barely sufficient. It does not tell the agent that the response is a paginated collection or that the endpoint is IaaS-scoped, which are the remaining gaps.

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% across all five parameters (top, skip, count, filter, apiVersion), so the schema already carries the semantics. The description adds nothing about pagination conventions or filter expression syntax, so the baseline 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?

"Get all deployments" states a verb and resource and the scope word "all" implies a collection listing rather than a single lookup, but it largely restates the tool name and gives no differentiation from the many deployment-related siblings (deployment_get_deployments, iaas_get_single_deployment, deployment_get_deployment_by_id).

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, despite several sibling tools that return deployments from a different service. The agent must infer from the name alone that this is the IaaS-side list endpoint.

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