airc_register

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states only that registration occurs, without mentioning side effects (e.g., idempotency, session state) or requirements (e.g., authentication). This is a significant gap for a mutation tool.

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 consists of two sentences with no wasted words. The first sentence states the core purpose, and the second adds crucial ordering guidance. It is efficiently front-loaded.

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?

For a registration tool with no output schema, the description should at least mention success/failure indicators or stored state. It omits critical context like whether the handle becomes permanently bound, recovery key handling, or potential errors. This leaves agents uncertain about the tool's full behavior.

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?

The input schema has 100% description coverage, so the schema already explains each parameter's meaning. The description adds no additional semantic value beyond the schema. Baseline 3 is appropriate given the high schema coverage.

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 'Register with the AIRC network' as the verb+resource combination. It also notes to call this first before sending messages, which differentiates it from sibling tools that perform other actions like sending or polling. However, it does not elaborate on what registration entails or how it relates to the network beyond ordering.

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 instruction 'Call this first before sending messages' provides clear usage context, implying it is a prerequisite for other operations. There is no explicit mention of alternatives or when not to use it, but given the sibling tool set, registration is a unique initial step with no direct alternatives.

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