delete-global-parameter

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

The description only says 'Delete,' which aligns with the readOnlyHint=false annotation indicating a destructive operation. However, it adds no further behavioral details such as idempotency, side effects, or error behavior. The annotations already imply destruction, so the description adds minimal value beyond that.

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 a single concise sentence. It is front-loaded and to the point. However, for a tool with one parameter, it could afford to include additional context without losing conciseness.

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?

Given the simple delete operation and lack of output schema, the description is minimally adequate. It covers the core action but misses details like return value, error scenarios, and prerequisites. For a sibling-heavy domain, more context would improve completeness.

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?

The input schema has a required 'name' parameter with no description. Schema coverage is 0%, so the description should compensate. The description fails to explain what 'name' refers to, its format, or constraints. This leaves ambiguity for the agent.

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 action and resource: 'Delete a global parameter.' It is specific and unambiguous, distinguishing it from siblings like 'delete-parameter' by the word 'global.' However, it does not elaborate on what a global parameter is, which could be clarified.

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 like 'delete-parameter' or 'put-global-parameter.' The description gives no context about use cases, prerequisites, or conditions under which deletion is appropriate.

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