update_wedding_settings

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

Annotations provide destructiveHint=false. The description adds partial update semantics (preserving unprovided fields), which is beyond annotations. It does not disclose permissions or error states, but the addition is valuable.

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 sentences, no redundancy. First sentence states purpose, second explains usage pattern. Efficient front-loading.

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 13 parameters, no output schema, and only destructiveHint annotation, the description covers core behavior. It lacks output specification and constraints but is sufficient for basic operation.

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 46%, with 6 of 13 parameters described. The description provides general guidance ('provide only fields you want to change') but does not detail individual parameters. This is acceptable but not exceptional.

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 top-level wedding settings', specifying the verb and resource. It distinguishes from siblings like get_wedding_settings (read) and other update tools (update_event, update_guest_address) by focusing on top-level settings.

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 explicitly says 'Provide only the fields you want to change; the rest are preserved', indicating partial update usage. While it doesn't enumerate when not to use, the context implies using this for top-level settings and other tools for specific updates.

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