update-slo

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

Explicitly states 'Fetches current SLO first to merge unspecified fields' and 'Write-gated', which are not in annotations. Annotations show readOnlyHint=false (consistent). Adds significant 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?

Two concise sentences: first states purpose, second adds key behavioral details. Front-loaded, no redundant information.

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?

Covers purpose, merge behavior, and write-gating. No output schema, so return values not needed. Could mention that it is a partial update (PATCH semantics), but overall complete for a 6-param tool with full schema.

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%, so baseline is 3. Description only lists parameter names, adding little beyond schema descriptions. Does not explain constraints like thresholds structure or monitorIds applicability.

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 states specific verb 'Update' and resource 'existing SLO', lists exact fields (name, description, thresholds, monitorIds, tags). Clearly distinguishes from siblings like create-slo, delete-slo, and update-slo-correction.

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?

Implies use for modifying existing SLOs, but lacks explicit when-to-use vs alternatives (e.g., create-slo for new, delete-slo for removal). Does not mention when not to use or provide exclusion criteria.

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