create_sla_definition

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds a meaningful requirement (WRITE_ENABLED=true) beyond the annotations, providing valuable operational context. It does not contradict annotations and offers additional behavioral insight.

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 extremely concise—two short sentences with zero filler. It front-loads the core purpose and immediately adds the key prerequisite. Every word earns its place.

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?

For a creation tool with 9 parameters fully described in the schema and annotations covering safety, the description is sufficient. It lacks details on return values, but no output schema exists. The WRITE_ENABLED requirement addresses a key operational constraint. Overall, it covers the essential context for correct invocation.

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 description coverage is 100%, so all 9 parameters are documented in the schema. The description does not add parameter-level meaning beyond the schema. Per the rubric, a baseline of 3 applies when the schema carries the burden, which it does here.

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 the verb (Create), the resource (SLA/OLA definition), and the specific table (contract_sla). It distinguishes itself from siblings like list_sla_definitions and update_sla_definition by specifying creation. The purpose is unambiguous.

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 provides a prerequisite (Requires WRITE_ENABLED=true) but does not explicitly state when to use this tool versus alternatives like update_sla_definition. It implies creation use case but does not mention exclusions or alternative selection criteria. Adequate but not explicit.

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