save_setting

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

Discloses merging semantics (data is merged, not overwritten) and access method. No annotations, so carries full burden; could mention idempotency or return value but still solid.

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?

Three sentences, no waste. Front-loaded purpose, then behavior, then usage hint. Ideal for quick scanning.

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?

Adequate for a simple create/update tool with no output schema. Covers purpose, behavior, and access. Lacks return value or error conditions but not critical for basic usage.

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?

Description adds meaningful context beyond schema: merging behavior and config() access pattern. Schema has 100% coverage, but description enriches understanding of how parameters interact.

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?

Clear verb+resource: 'Create or update a setting profile.' Distinguishes from sibling tools (delete_setting, get_setting) by being the sole create/update tool.

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?

Mentions merging behavior and access pattern via config(). Implicitly distinguishes from delete and get siblings, but lacks explicit when-to-use vs. when-not-to guidance.

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