queue_queue_size

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

No annotations are provided. The description does not disclose whether the operation is read-only, requires special permissions, or what happens if the queue doesn't exist. For a simple read operation, basic transparency is missing.

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?

Extremely concise, with one meaningful sentence and a helpful '[queue]' prefix. No excess words; every part serves a purpose.

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 size-checking tool, the description is minimally adequate. However, it lacks parameter explanation and usage guidance, and the absence of annotations means it should carry more behavioral context. An output schema exists but is not described.

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 0% description coverage for the 'name' parameter. The description does not explain what 'name' refers to (e.g., queue name or ID), leaving ambiguity. The description adds minimal value beyond the schema itself.

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 returns the number of items in a queue. It uses a specific verb ('Return') and resource ('number of items'), and distinguishes from sibling tools like queue_queue_peek, queue_queue_pop, etc., by focusing on size.

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 on when to use this tool versus alternatives like queue_queue_list or queue_queue_peek. There is no mention of context or exclusions, leaving the agent to infer usage from the name alone.

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