sage_register

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

The description discloses idempotency and the creation of an on-chain identity. With no annotations, it provides useful behavioral context, though it could mention authorization or side effects (e.g., transaction costs).

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?

Three concise sentences that front-load the purpose, then provide usage guidance and behavioral note. Every sentence adds value without 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?

The description covers the core action, when to use, and key behavior. It lacks return value details and prerequisites (e.g., wallet connection) but is sufficient for a simple registration tool.

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%, and the description restates the parameters (name, optional bio) without adding new meaning beyond the schema. Baseline score of 3 is appropriate since the schema already fully describes them.

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 the tool's purpose: register an agent on the SAGE chain, creating an on-chain identity with a name and optional bio. It uniquely identifies the action and distinguishes from siblings like sage_list or sage_status.

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 mentions that this is called automatically on first connection and that manual invocation is rarely needed. Also notes idempotent behavior, giving clear guidance on when to use.

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