he_update_description

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

Discloses key behavior: 'Omitted fields are preserved: current values of the target locale are merged in before the PUT'. Without annotations, this reveals the merge (non-destructive update) and locale behavior. Asks for user confirmation, indicating caution. Contradiction: false.

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 concise sentences with a crucial note. No redundant words. Action and key details are front-loaded.

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?

Covers merge behavior, locale usage, and confirmation requirement. With 6 parameters and no output schema, the description is sufficient. Could mention return value or error handling, but not critical for selection/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 coverage is 100%. Description adds value beyond schema by explaining merge behavior for omitted fields and locale usage. Lists the updatable fields and clarifies that locale creates or updates a specific language version.

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?

States 'Update property description texts' with specific fields listed (title, good_feature, good_place, other). Verb+resource is precise. Distinguishes from sibling tools like he_update_home which updates broader home 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?

Explicitly instructs to 'ask user confirmation' and explains 'Use locale to create or update a specific language version'. Provides clear context for when to use locale. Does not explicitly exclude scenarios or name alternatives, but the confirmation note is a strong usage guideline.

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