set_password

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the bare mutation. It does not explain whether the password protects opening or modifying the document, whether it replaces an existing password, or what side effects occur on save.

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 minimal and front-loaded: a single purpose sentence followed by a compact Args list. Every sentence earns its place with no unnecessary filler.

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 security-sensitive mutation with no annotations, the description is too thin. It omits behavioral consequences, security caveats, and the important ambiguity of whether the password is for opening or editing, and the noted output schema does not compensate for this missing context.

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 description coverage is 0%, so the description must compensate for missing parameter meaning. It usefully identifies doc_id as a document ID from open_document and password as the string to set, but it adds no constraints on password length, encoding, or allowed values beyond the schema's string type.

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 uses a specific verb and resource ('Set document password') and clearly names both required arguments. However, it does not explicitly distinguish itself from nearby sibling tools like set_file_security, so an agent may not know which password-related tool to select.

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?

There is no when-to-use guidance or comparison to alternatives. The only contextual hint is that doc_id comes from open_document, but the description never tells the agent when to prefer set_password over set_file_security or set_drm_authority.

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