Provision agent token

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

Description states starting a free device trial, which is a side effect, but the annotation declares readOnlyHint=true. This contradiction misleads about whether the tool modifies state. Per rubric, contradiction yields score 1.

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 a single sentence that packs all essential information: purpose, duration, fallback, and return value. It is front-loaded and concise, with no wasted words.

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 simple tool with one optional parameter and no output schema, the description covers the return value (token_prefix and expiry), explains authentication, and notes the 12-hour validity. It is complete for the agent to use the tool correctly.

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 a clear description for the refresh parameter. The description adds context about the environment variable fallback, which helps understand when refresh might be useful, beyond what the schema alone provides.

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?

Description clearly states the tool obtains a 12-hour ngsrv agent token for tunnel commands. It specifies the verb, resource, duration, and purpose. It is well-distinguished from sibling tools like tunnel.list or tunnel.start.

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?

Description explains when to use this tool (for tunnel commands) and describes fallback behavior (uses environment variable or starts free trial). However, it does not explicitly state when not to use or mention alternatives, but given sibling tools are different, the context is sufficient.

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