update_salutation

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive nature is captured. The description 'Edit a salutation' adds no additional behavioral context such as permission requirements, side effects, or return behavior. It is largely redundant with the tool name.

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 a single concise sentence with no filler words. It is front-loaded with the verb and object. While extremely brief, it is not verbose or poorly structured; it simply lacks 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?

For a simple update tool with two parameters and annotations, the description is thin. It doesn't mention what happens when editing, whether the name is the only updateable field, or any success/error implications. The context provided is barely more than the tool name itself.

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?

The schema describes 'salutation_id' but not 'name'. The description fails to explain what 'name' represents or how it relates to a salutation. With 50% schema description coverage, the description should compensate but does not add any parameter-level meaning.

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 action 'Edit' and the resource 'a salutation', making the purpose unambiguous. It distinguishes itself from create/delete/get/list/search siblings by the verb, but doesn't explicitly call out the distinction. It's specific and understandable.

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 gives no guidance on when to use this tool versus alternatives like create_salutation or update_title. There is no mention of prerequisites, exclusions, or appropriate contexts. The agent must infer usage solely from the tool name and schema.

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