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

No annotations provided, and description only states 'check parent approval, activate Authority'. It does not disclose whether activation is destructive, permissions needed, or any side effects. Minimal behavioral context.

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?

Description is single sentence, front-loads 'Step 3/3', and is efficient with no waste.

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?

Output schema exists, so return values are covered. However, missing context about prerequisites, error scenarios (e.g., parent approval failure), and relationship to other onboarding steps. Adequate but incomplete.

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 coverage is 100% with one parameter described. Description does not add meaning beyond the schema description of candidate_npub. Baseline 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?

Description states it is 'Step 3/3 of Authority onboarding' and specifies two actions: 'check parent approval' and 'activate Authority'. The verb+resource is clear, but it does not differentiate from sibling tools like authority_get_operator_onboarding_status or authority_register_operator.

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?

Implied by 'Step 3/3' that it is used after prior steps, but no explicit guidance on when to use vs alternatives or exclusions.

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