deployment_check_deployment_name_exists

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the useful return semantics ("Returns OK if a deployment with the supplied name exists") plus the underlying GET endpoint, though it never says what an agent sees on the negative path (404, error, or empty result).

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?

Three short, front-loaded sentences with no filler; the purpose is stated first and the return condition second. The trailing raw endpoint line largely duplicates the annotation title and is the only redundancy.

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?

No output schema exists, so the description must carry return-value semantics; it does state the OK case but leaves the not-found case and the response shape undefined. For a trivial one-parameter existence check this is minimally adequate but not fully complete.

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?

There is a single parameter and schema description coverage is 100% ('Deployment name'), so the schema already does the work. The description's mention of 'the supplied name' adds no format, scoping, or naming-convention detail beyond it.

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 states a specific verb and resource (check whether a deployment with a given name exists) and is clearly narrower than the sibling getters like deployment_get_deployment_by_id or deployment_get_deployments. It doesn't explicitly contrast with the similarly named deployment_check_deployment_name sibling, so a 4 rather than a 5.

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 statement of when to use this existence check versus alternatives such as deployment_get_deployment_by_id or deployment_check_deployment_name, nor any prerequisite or ordering guidance. Usage is only implied by the one-line purpose.

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