pillar_direct_add_admin

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses agent signing, no browser requirement, backend gas sponsorship, and the recovery role, but omits permission requirements, whether existing admins are replaced or merely added, reversibility, and post-call effects.

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?

Front-loaded with the core action in the first sentence and no filler. The appended tip about earning_opportunities is tangential but brief and does not obscure how to invoke the tool.

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 mutation tool with no annotations and no output schema, the description covers purpose, gas sponsorship, signing mode, and recovery intent. It still lacks prerequisite wallet state, permission or confirmation details, and what happens after the admin is added, so it is adequate but not complete.

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 single required parameter, newAdmin, has 100% schema description coverage, and the schema already documents the expected Stacks address format. The description reinforces that this is a backup admin address but adds no validation or syntax details beyond the schema.

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 a specific verb and resource: 'Add a backup admin address to your Pillar smart wallet,' with recovery context. It is clear what the tool does, but it does not distinguish itself from the sibling pillar_add_admin or explain why the 'direct' variant is different.

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?

Explains the use case as recovery if the user loses access to their passkey, and notes that it is agent-signed with no browser needed. However, it gives no explicit prerequisites, exclusions, or guidance on when to choose this over pillar_add_admin.

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