save_statement

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

No annotations are provided, so the description must fully disclose behavior. It indicates mutation ('Update'), but omits critical details: whether the operation is idempotent, partial vs full update, error handling for non-existent uuid, authorization requirements, or side effects. The description is too brief to ensure safe agent invocation.

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) and front-loaded with the action. Every word is relevant; there is no redundancy or unnecessary elaboration.

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 no output schema, the description should inform about return values (e.g., updated statement or success status) or error behavior. It does not. For a mutation with 2 parameters and nested objects, the description is incomplete, lacking confirmation of success or failure states.

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?

Both parameters are described in the input schema (100% coverage). The description adds no new meaning; it merely restates the schema's 'Statement data to update' for the 'data' parameter. For the 'uuid' parameter, the description doesn't provide additional context (e.g., where to find it). With high schema coverage, baseline is 3, and the description adds no extra value.

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 'Update an existing statement', which identifies the verb (update) and resource (statement). It implicitly distinguishes from 'create_statement' and 'delete_statement', though it doesn't explicitly name siblings. The phrase 'modify statement properties after creation' reinforces the update purpose.

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 implies usage for modifications ('after creation'), but does not explicitly state when not to use (e.g., for new statements use 'create_statement'). It lacks prerequisites (e.g., statement must exist) and does not offer alternatives among siblings.

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