exchange_get_queue_digest

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

With no annotations, the description must carry behavioral details. The 'Get' verb and 'digest' wording reasonably signal a read-only, aggregate operation across the DAG, but the description does not disclose what data the digest contains, whether it is aggregated, or any permission/error 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?

One short sentence front-loads the action, resource, and scope with no filler or redundant explanation. The parenthetical cmdlet name adds useful canonical context without bloating the description.

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 low-complexity tool with one optional parameter and no output schema, the description is minimally sufficient: an agent can infer it returns a DAG-wide queue summary and may pass a dag value. However, the missing parameter semantics and lack of any output description keep it from being fully complete.

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 0%, so the description needed to explain the dag parameter, but it only repeats the word DAG. It does not clarify whether dag is a filter, how to format a DAG identifier, or what happens when the parameter is omitted.

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 action ('Get') and resource ('queue digest') with an explicit scope ('across DAG'), making it distinguishable from the more targeted sibling exchange_get_queue. It would be a 5 if it explicitly described what a digest contains or contrasted itself with queue-level retrieval.

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 usage guidance is provided. The description does not say when to use this instead of exchange_get_queue, exchange_suspend_queue, or the other siblings, nor does it specify conditions or exclusions; the only contextual signal is the 'across DAG' scope.

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