sage_register

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

With no annotations, the description carries the full burden. It discloses idempotency and notes that it returns an existing record if already registered. This adds behavioral context beyond the schema, though it could mention potential side effects like chain transactions or permissions.

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?

The description is compact with three sentences, each contributing meaning. It is front-loaded with the primary action and efficiently covers purpose, usage guidance, and idempotency without redundancy.

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 tool's simplicity (two parameters, no output schema, no annotations), the description covers key aspects: action, usage frequency, and idempotency. It could be improved by describing the return format or potential errors, but it remains adequate for effective use.

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 descriptions for both parameters. The description adds value by explaining that the parameters form an on-chain identity and that boot_bio is optional, reinforcing the schema info. It does not introduce new parameter details but contextualizes them well.

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: registering the agent on the SAGE chain and creating an on-chain identity with a name and optional bio. It distinguishes from sibling tools by focusing on registration and noting it is normally called automatically.

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?

The description provides explicit guidance that the tool is rarely called manually because it is invoked automatically on first connection. It does not explicitly list alternatives or when not to use, but the context is clear enough for an agent to determine appropriate usage.

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