addPerformanceMonitors

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

Without annotations, the description fails to disclose any behavioral traits such as whether the operation is additive, idempotent, or what happens on conflict. No information about authentication, rate limits, or side effects is provided.

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 truncated mid-sentence and lacks any cohesive structure. It is not concise but incomplete, failing to communicate the tool's purpose or parameters fully.

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 description is wholly inadequate for a tool with four required parameters and no output schema. It lacks information about return values, error handling, or behavior, leaving the agent without sufficient context to use the tool correctly.

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 description only incompletely covers two of four parameters (name and selectedMonitors), with selectedMonitors description truncated. It adds no value beyond the input schema for the covered parameters and omits host and apiKey entirely.

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 does not explicitly state what the tool does; it only lists key parameters without a clear verb phrase or purpose statement. The tool name implies adding performance monitors, but the description lacks a definitive action description.

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 versus sibling tools like deletePerformanceMonitors or getPerformanceMonitors. The description does not mention context, prerequisites, or alternatives.

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