create-slo

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

No annotations are provided, so the description must carry the full burden. It only notes 'Write-gated' but fails to disclose other behavioral traits such as side effects, authentication, rate limits, or what happens upon creation (e.g., return 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?

The description is very short (one sentence plus a note), achieving conciseness. Every word counts, but it could be front-loaded with more critical context without becoming verbose.

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 complexity of the input schema (9 parameters, nested objects) and no output schema, the description is incomplete. It omits critical information such as the return value (e.g., created SLO ID), validation rules, and error handling. The 'Write-gated' note is insufficient.

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 individually described parameters. The description adds no extra meaning beyond listing the three SLO types already present in the schema's enum. Baseline score is appropriate as the description does not enhance parameter understanding.

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 'Create a new Service Level Objective' with specific types (monitor-based, metric-based, time-slice), distinguishing it from other create-* tools on the server. The verb and resource are explicit.

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?

The description only mentions 'Write-gated', which hints at permission requirements but does not specify when to use this tool versus alternatives like update-slo or delete-slo. No explicit context or exclusion criteria are provided.

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