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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the useful domain context that resources are 'scarce' and 'defined by people' and that held/queued slot counts are surfaced, but says nothing about ordering, filtering, or pagination 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 fragment with no wasted words, but it is grammatically incomplete and front-loads an adjective ('Scarce') instead of the action, which slightly delays comprehension. Brevity is fine; the structure is what costs it.

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?

Consider a zero-parameter read-only list tool with an output schema, annotations, and no configuration. The description supplies the domain framing ('scarce resources defined by people') that the schema cannot, and the return shape is covered by the output schema. Nothing needed to call it correctly is missing.

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 no parameter semantics to explain and the baseline of 4 applies. The description's mention of 'held and queued' slots is a bonus hint about what the caller will see rather than required input detail.

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 text is a noun phrase ('Scarce resources defined by people, with how many slots are held and queued') rather than a verb+resource statement, so the listing action is only implied by the tool name. It does convey what a resource is and what data comes back, which helps separate it from acquire_resource/release_resource, but the agent must infer 'lists all resources' from the name alone.

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?

There is no when-to-use guidance at all: nothing says to call this before acquire_resource to find a free slot, nor any mention of alternatives or prerequisites. The only routing signal is the tool name against its siblings.

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