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

With no annotations, the description carries the burden of behavioral disclosure. It adds valuable context by noting the tool is free, exposes no per-expert PII, and provides real-time counts and wait estimates. It does not explicitly state read-only behavior, but 'Returns' and the absence of any side effects imply it, so a small gap remains.

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?

The description is three sentences, front-loaded with the main output, then usage guidance, then a privacy note. Every sentence adds value with no redundancy or fluff.

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?

The tool is simple: no parameters and an output schema exists. The description fully covers what is returned (taglines, seat count, wait), the nature of the data (pseudonymous, no PII), and the cost (free). There are no gaps in understanding when or why to use it.

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 has zero parameters, so the baseline score is 4. There is no parameter information to add, and the description appropriately focuses on outputs and usage. The schema is empty, so nothing is undocumented.

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 clearly states a specific verb ('Returns') and resource ('expert taglines') along with additional data (online seat count and estimated wait). It distinguishes itself from sibling paid tools by framing itself as a cheap pre-flight check, making the purpose unambiguous.

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 explicitly says 'Use this as a cheap pre-flight check before calling a paid tool,' which specifies when to use it and implies not to call paid tools first. This is clear usage guidance, even though specific sibling names are not mentioned.

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