Capacity of the meeting bot

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

With no annotations and no output schema, the description carries the full burden; it does usefully disclose the shape of the answer (level values, seated/waiting lists, future clashes within a horizon) which an agent could not otherwise know. It says nothing about freshness guarantees beyond 'latest', cost, or that the call is a non-mutating read, leaving gaps for a zero-annotation tool.

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 tight sentences: the first front-loads what the payload contains, the second front-loads when to call. Nothing is redundant with the name or title, and there is no filler.

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 no-parameter, no-output-schema read tool, the description gives enough — what comes back and when to reach for it — to invoke it correctly. It could go further by clarifying whether the 'horizon' is fixed or whether the snapshot is live versus cached, but nothing essential 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 the baseline is 4. The description doesn't need to explain inputs, and the mention of a 'horizon' doesn't create a parameter the agent must supply.

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 names a specific resource (the latest capacity picture) and enumerates what it contains: level (ok/near/reached), who is seated, who is waiting, and future clashes within the horizon. That is far more specific than a sibling like 'status' or 'meeting_status', though it doesn't explicitly say how it differs from those.

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?

It gives concrete triggers — 'on connect' and 'when the human asks' — which is real when-to-use guidance rather than an implied purpose. It stops short of exclusions or naming an alternative (e.g., status vs meeting_status) for capacity questions.

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