poa_register

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

With no annotations, the description carries the full behavioral burden and does so excellently: it discloses file creation with permissions (0600), that the key is never returned, the default referral behavior, the economic impact (up to 20% of payout from your share), and how to opt out. No critical traits are hidden.

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-loads the core action and effect, then uses a clearly delineated 'REFERRAL DISCLOSURE' block for the crucial monetary/default-routing details. Every sentence is necessary and well-organized.

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?

Given the complexity (account creation with referral economics), no output schema, no annotations, and 0% schema coverage, the description is nearly complete. The main gap is the missing 'label' parameter explanation; minor omissions like error behavior (e.g., if already registered) are acceptable.

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 explain all parameters. It fully defines 'referrer' and 'no_referral', but the required 'label' parameter is never mentioned, leaving an agent guessing what value to provide.

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+resource ('Create a PoA account') and the exact side effect ('save its API key to a local 0600 file'). Clearly distinguishes itself from all siblings, which are operations on an existing account rather than registration.

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?

Implies single use via 'One account per agent' and gives explicit conditions for referral options ('Set no_referral=true to opt out, or referrer=...'). Does not state when to call versus alternatives (none exist for registration), but the guidance present is clear and actionable.

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