Disable the active environment customImage template

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

Annotations already indicate destructive and idempotent behavior (destructiveHint=true, idempotentHint=true, openWorldHint=true). The description adds the authorization class and HTTP method but does not explain side effects, what 'disable' entails, or what happens to running environments. The open world hint suggests undisclosed behavior.

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 very concise—two sentences that state the purpose and provide the HTTP operation and authorization. It is front-loaded with the main action. However, it is too brief to cover other dimensions, but for conciseness alone it earns a high score.

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?

Despite having 3 parameters (one nested object), an output schema, and being destructive with open world hints, the description fails to provide sufficient context. It does not describe the output, success/failure behavior, parameter details, or side effects. The output schema exists but is not leveraged in the description.

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 only 33% schema description coverage, the tool description does not explain the meaning of parameters. The body parameter's schema description is about the schema, not its purpose. The path (environmentId) and query (companyId, deleteProviderTemplate) parameters lack any explanation of their roles, leaving the agent to infer from schema structure alone.

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 title and description clearly state the tool disables the active environment custom image template, with the HTTP method and endpoint provided. It differentiates from sibling tools like environment deletion or template creation/retrieval. However, using 'disable' instead of 'delete' introduces slight ambiguity about the operation's permanence.

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 guidance is provided on when to use this tool versus alternatives (e.g., pc_delete_environments_by_id or the GET/POST for custom image templates). Prerequisites (e.g., environment must exist, template must be active) and consequences of multiple calls are not mentioned.

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