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

With no annotations, the description carries the full burden and does disclose non-obvious traits: it is 'Free' (cost), and it is 'built only from what the latest access audit unlocked,' which tells the agent the result depends on prior access-audit state and may be empty or stale otherwise. It also specifies the ordering ('ranked') and time scope ('this week'). It omits auth requirements and pagination/refresh behavior.

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?

Three short sentences, front-loaded with what the queue is, then its fields, then cost and consumption rule. Every sentence carries information; the inline field list is the only slightly clunky element, but it is compact and useful.

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?

No output schema exists, so the description must explain the return value, and it does so by naming all six fields and the ranking ordering. Combined with the zero-param schema and the stated data dependency, an agent has enough to call and interpret it; only edge cases (empty queue, stale audit) are left implicit.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a 0-param tool is 4. The listed tuple describes the return shape rather than inputs, which adds clarity without conflicting with the empty schema.

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 states a specific resource and scope: 'the ranked queue for this week,' and enumerates the fields it contains ({rank, module, title, why, command, credits}), so an agent knows exactly what it gets back. It is clear but stops short of naming a sibling (e.g. visibility, goals, access) or explicitly saying how this differs from those plan-like tools.

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?

'Work it top down; state the credits before running anything priced over 5' gives real guidance on how to consume the output and a cost gate before spending. However, it offers no guidance on when to call this tool versus alternatives, no prerequisites, and no exclusions, so tool-selection guidance is only implied.

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