List Edge Compute deployments

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

The '[READ]' prefix merely duplicates readOnlyHint=true, and nothing is said about pagination, result ordering, or what happens when the edge compute has no deployments. With annotations already covering the safety profile, the description contributes almost no behavioral context beyond the HTTP verb.

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 a single front-loaded line with zero waste, but this is brevity by omission rather than disciplined conciseness. The '[READ]' tag is the only structured signal before the raw path.

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 list tool with no output schema, the description should indicate the shape and pagination of results and the meaning of the scoping id. Neither is present, so an agent cannot predict the response or confidently construct the call beyond copying the schema.

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% and the single parameter edge_compute_id carries no description in either the schema or the description text. The path fragment implies the id is a path parameter scoping the query, but no format, source, or constraint (e.g. where to obtain a valid id) is given.

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 identifies a read operation against the deployments sub-resource of a specific edge compute via the raw path GET /edge-computes/{edgeComputeId}/deployments, which adds the scoping relationship that the bare name 'list_edge_deployments' does not convey. However, it never states what a 'deployment' is or what is returned, so it remains a near-restatement of the endpoint rather than a full purpose statement.

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. Siblings such as get_edge_compute, deploy_edge_compute, list_edge_computes, and list_caas_deployments make it non-obvious which listing tool an agent should choose, and the description offers no routing help.

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