account_permission_update

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds that it sets owner, active, and optional witness permissions, providing some scope context. However, it does not state whether the update replaces existing permissions or merges them, nor does it disclose additional side effects beyond the annotation.

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 two concise sentences, front-loaded with the action and purpose, and free of redundant wording. Every word carries meaning.

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?

The tool is complex, but the schema and annotations cover the detailed configuration thoroughly. The description communicates the overall scope and optional witness permission, though it could clarify whether the update is a full replacement or partial. No output schema exists, but this is a mutation tool, so return behavior is less critical.

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 100%, and the schema provides detailed descriptions for all parameters including nested structures. The description only mentions the permission types at a high level, adding little beyond what the schema already states. Baseline score of 3 is appropriate.

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 the specific verb 'Update' with the resource 'account permissions' and clearly states the purpose ('multi-signature configuration'). It enumerates the permission types (owner, active, optional witness), distinguishing it from sibling tools like update_account or update_contract_setting.

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 clearly indicates the context for use ('multi-signature configuration') but does not explicitly mention when not to use it or provide alternative tool names. It gives clear context without exclusions, so it earns a 4 rather than a 5.

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