ise_set_default_deployment

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description states this is a mutating/setting operation, suggesting a state change, but doesn't disclose whether this persists across sessions, affects other callers, is reversible, or what the return/response looks like. For a state-mutation tool with zero annotation coverage, more behavioral detail would be valuable.

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?

A single concise sentence that front-loads the core purpose. Zero waste, no redundant restating of the tool name, and the sentence earns its place by adding the key qualifier about unnamed tool calls.

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?

The tool is a simple state-setter with one parameter and no output schema. The description adequately covers the primary function. However, it could benefit from noting whether this is a per-session or persistent setting, which would matter given the absence of annotations. Still, for a single-parameter tool, the description covers the essential purpose reasonably well.

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 coverage is 100% with one parameter ('deployment' - Name, slug, or number to make the default). The description adds the semantic context that this parameter identifies the deployment to change. However, it doesn't clarify what formats are acceptable (name vs slug vs number) or how to reference the current default. The schema baseline of 3 applies since schema fully documents the parameter.

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 the tool's purpose: setting which deployment is used by default when a tool call doesn't name one. This distinguishes it from related deployment tools (add/update/remove/list) and test_deployment. However, it doesn't explicitly state the resource target (e.g., 'sets the default deployment for this session/connection') or contrast with siblings like ise_add_deployment.

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?

No when-to-use guidance is provided. It doesn't explain when one would set a default deployment versus passing an explicit deployment per call, nor does it reference sibling tools like ise_list_deployments or ise_test_deployment for context. The phrase 'used when a tool call does not name one' implies usage context but provides no explicit recommendations or exclusions.

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