serve_deployment_list

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

The description marks the tool as '[READ]' hinting at read-only behavior, but with no annotations provided, the description carries full burden. It fails to disclose pagination, error handling, or any side effects. For a list operation, it lacks depth.

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 extremely concise (two lines), with the purpose front-loaded via the '[READ]' marker and a clear list of returned fields. No extraneous information.

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 list tool with no output schema, the description adequately states what it returns but omits format, ordering, or filtering details. It is minimally complete for its complexity.

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?

With 0% schema description coverage, the description compensates by explaining the 'target' parameter: 'Inference target name from config; omit for the default.' This adds real context beyond the schema's type definition.

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 it lists 'All Ray Serve deployments' with specific fields (status, replica count, target). It uses a specific verb ('list' implied by '[READ]') and resource ('deployments'), and the 'All' qualifier distinguishes it from tools that focus on single deployments or replicas.

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?

Only basic parameter usage is given ('omit for the default'). No guidance on when to use this tool versus sibling tools like deployment_status or replica_list, nor any prerequisites or context for invocation.

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