deletePerformanceMonitors

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'deletePerformanceMonitors' and lists two parameters. It does not mention that the operation is destructive, requires authentication, or what happens after deletion. The description provides minimal behavioral context.

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 short but appears truncated. It starts with the tool name, then a category line, then a list of only two out of four key parameters. The structure is incomplete and does not provide a coherent summary.

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 four required parameters, no output schema, and no annotations, the description should fully explain the tool's purpose and behavior. It fails to do so, omitting critical details like the need for host and apiKey, the effect of the operation, and any usage constraints. The description is drastically incomplete.

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 schema has full coverage (100%) of all four parameters, so the baseline is 3. The description lists only two parameters (name and pollId) and omits host and apiKey, but the schema already provides complete descriptions. However, the description adds no additional meaning beyond the schema, so it neither improves nor degrades the semantic value.

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 repeats the tool name 'deletePerformanceMonitors' and adds a generic category line. It does not clearly state that the tool deletes performance monitors from a device, nor does it distinguish it from sibling tools like getPerformanceMonitors or addPerformanceMonitors.

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 on when to use this tool compared to alternatives. There is no mention of prerequisites, scenarios, or exclusions. The description fails to help an agent decide when to invoke this tool over other delete or monitor-related tools.

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