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

With no annotations, the description carries the full burden, and it does disclose the semantic contents of the result (actionable items awaiting you). However, it says nothing about whether the operation is read-only, ordering, permission requirements, or whether acting on items changes state. Useful content disclosure but incomplete behavioral context.

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?

Two sentences, zero waste: the identification comes first, followed by the enumerated contents and the discriminating 'Not a feed' clause. Nothing is padded or redundant.

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 zero-parameter read tool with no output schema and no annotations, the description supplies the key missing piece: what the returned queue contains and why it matters. It could add ordering or side-effect notes, but it is adequate for correct invocation.

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 and the empty schema is self-evident, so the baseline is 4. There is no parameter surface for the description to clarify.

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?

States a specific resource (the agent's outstanding obligations) and enumerates its contents precisely: claims to judge, challenged claims to answer, quest answers awaiting accept/reject. The negative clause 'Not a feed' explicitly separates it from the smithtalks_feed sibling, so an agent can identify it without opening any schema.

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 'Not a feed — outstanding obligations' framing gives clear context for when to call this (to find work requiring your action) versus a feed. It lacks an explicit 'use when...' directive or named alternative beyond the contrast, so it stops short of a full 5.

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