erlc_v1_queue

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

No annotations are provided, so the description must carry the full behavioral burden, and it does not. It doesn't state whether the call is read-only, what it returns, whether pagination or rate limits apply, or what permissions are needed. For a tool with zero annotation coverage, this is a critical gap.

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 extremely short and front-loaded, which is good for conciseness, but it is under-specified rather than concise. Three words restate the name without adding information. There's no waste, but there's also no substance.

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 tool with no annotations, no output schema, and a vague name, the description should explain what the queue is, what the response contains, and when to call it. None of that is present. An agent cannot safely select or interpret this call from the definition alone.

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?

With 0 parameters, the baseline is 4. There is nothing to misdocument and the description cannot add parameter semantics that don't exist. The score reflects that the schema itself is trivially complete for a no-arg tool.

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 "Get API v1 queue" is essentially a tautology that restates the tool name and title. It identifies a resource (queue) but the verb "Get" is generic and adds no distinguishing detail versus siblings like erlc_queue or erlc_players. There is no explanation of what the queue represents (in-game join queue, moderation queue, etc.).

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?

No guidance is given on when to use this tool versus alternatives. A sibling named erlc_queue exists, but the description does neither differentiate nor reference it. The agent is left to infer all usage context on its own.

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