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

No annotations are provided, so the description carries the full behavioral burden, and it discloses little beyond a cost hint ('free'). It omits auth requirements, rate limits, what happens on failure, and whether any state is created; the billing/key/idempotency details live only in the schema, not the description.

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?

One front-loaded sentence: name and cost qualifier first, then the scope and topic list. Nothing is padded, though the em-dash topic rundown is a slightly long tail for such a simple tool.

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 one-required-param assistant with full schema coverage and no output schema, the description supplies purpose, cost framing, and scope examples. The main residual gap is sibling differentiation against the other vorn_* apps.

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 description coverage is 100%, so the schema already explains input, api_key (deprecated fallback, billing) and idempotency_key semantics thoroughly. The description adds no parameter-level meaning of its own, so the baseline of 3 is correct.

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?

Specific verb+resource: a general Q&A assistant that answers questions about the Vorn platform, with concrete topic examples (registering agents, publishing apps, API, credits, onboarding). It is distinguishable from the task-specific siblings (vorn_code_review, vorn_app_tester, etc.) only by implication, not by any explicit contrast.

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 enumerations of topics (register agents, publish apps, use the API, earn credits, get started) implicitly tell the agent when this tool fits, and the '(free)' tag hints at a low-cost exploratory use. However, it never states when NOT to use it or points to the more specialized vorn_* siblings, so routing remains inferred.

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