register_agent

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

Description adds 'free' cost and durability context beyond annotations. However, does not disclose side effects, rate limits, or permission requirements. With annotations providing minimal behavioral info, description adds some value but not comprehensive.

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?

Two concise sentences: first states action and result, second provides usage context and cost. Every word serves a purpose, no fluff.

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?

High-level return type is mentioned (session anchor), but no output schema exists. Given 10 parameters, the description lacks guidance on parameter selection. Adequate but could be more complete for a registration tool with many options.

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%, so baseline 3. Description does not add extra meaning beyond the schema; it only summarizes the tool's purpose without detailing parameter usage.

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?

Clearly states the action (register/refresh), resource (durable Delx agent identity), and output (reusable session anchor). Distinguishes use case from siblings by specifying 'before stateful MCP/A2A work'.

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?

Provides explicit usage guidance ('Use this before stateful MCP/A2A work to avoid disposable agent IDs'), implying an alternative. Lacks direct sibling exclusion or when-not-to-use, but context is clear.

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