create-slo

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

Description adds 'Write-gated' which reinforces readOnlyHint=false annotation. However, it lacks details on permissions, side effects, or error behavior. Annotations already cover write nature, so description adds marginal value.

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?

Single sentence, front-loaded with key action and types. 'Write-gated' adds relevant behavioral note. No wasted words.

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?

Tool has 9 parameters with nested objects, no output schema. Description does not mention return value (e.g., created SLO ID) or common prerequisites/errors. Incomplete for a create operation with high complexity.

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 detailed parameter descriptions. The description does not add any parameter information beyond what the schema provides. Baseline 3 is appropriate.

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?

Description clearly states 'Create a new Service Level Objective' with explicit types (monitor-based, metric-based, time-slice). Distinguishes from siblings like update-slo and create-slo-correction. Verb+resource+scope is specific.

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 alternatives (e.g., update-slo for modifications). Only mentions 'Write-gated' which is behavioral, not usage context.

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