build_disable_master_unsigned

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

Discloses it is unsigned, irreversible, runs an internal readiness check, fails closed, and never signs. No annotations provided, so description carries full burden and handles it well.

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?

Every sentence adds value: step context, action, irreversibility, internal check, failure condition, signing behavior. No wasted words.

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 purpose and preconditions well but lacks parameter explanations and expected return format (e.g., unsigned transaction blob). Adequate but has gaps.

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 does not explain the two parameters (account, network) despite 0% schema description coverage. Account is implied but not explicitly linked to the parameter.

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 clearly states it builds an unsigned AccountSet to disable the master key, and identifies itself as step 3 of the rotation wizard, distinguishing it from sibling build_* tools.

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 states irreversibility and precondition that an alternative signer must exist; implies when not to use without naming alternatives.

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