Update Password

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

Goes well beyond the annotations by disclosing PUT semantics: only supplied fields are sent and their new values replace the old ones outright. It also warns of overwrite risk and names hudu_get_password as a safety measure, adding meaningful behavioral context not present in the structured fields.

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 compact and front-loaded, with three short paragraphs that each earn their place: purpose, PUT behavior warning, and a terse operation/impact summary. No redundant or filler text is present.

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 14-parameter update tool with a richly detailed input schema, the description covers purpose, mutation semantics, and update strategy effectively. While there is no output schema and return behavior is not described, the core risks and usage are sufficiently addressed, leaving only minor gaps around response expectations.

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 already provides 100% descriptive coverage for all parameters, so the baseline is 3. The description adds crucial semantics about how parameters are applied (only supplied fields are sent, replacements are outright), which clarifies behavior for every parameter even though it does not detail each field individually.

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?

Clearly states 'Update an existing password' and explains what a password record is in Hudu, including API vs interface terminology. The verb and resource are specific and the tool is distinguishable from its create/get/archive siblings.

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 recommends reading the record first with hudu_get_password when intending to append, which is a concrete usage guideline. The description implies updating existing records rather than creating new ones, but does not explicitly state when not to use it or mention alternatives like hudu_create_password.

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