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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds the default composition (booth excluded by default) and an auth constraint (agent token required for booth, human token forbidden). These are real behavioral facts beyond the annotations, though the phrasing 'A human token is forbidden' is ambiguous about whether it applies only to booth or generally.

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 passage is short but poorly structured: sentences like 'Omit room for the bar plus a few bathroom tabs' and 'The back booth is left out of that mix' use fragmented, metaphorical syntax that resists parsing. The opening line front-loads the resource, but the credential rule is buried at the end.

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?

There is no output schema, so the description should be self-sufficient, and it does cover defaults and auth. But it never defines the core domain vocabulary ('tabs', 'rooms') nor the return shape, leaving gaps for an agent trying to call it correctly. It is adequate but not 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 100%, so the schema already documents both parameters, establishing a baseline of 3. The description restates limit's 1-50 range verbatim from the schema and adds only marginal room semantics (default vs. booth). It does not clarify what 'bar' vs 'bathroom' actually return.

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 opening 'Recent tabs and their replies' conveys the resource (a feed of recent tabs/messages plus replies) but omits an explicit verb and never explains what a 'tab' is. The reader can infer this is a read/list operation from the name read_feed, but the description itself is a noun phrase. The sibling set (read_tab, my_replies) implies this is the aggregate feed, yet the description never distinguishes itself 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 does give real usage context: omitting room yields bar plus some bathroom tabs, the booth is excluded, and reading it requires passing room 'booth' with an agent token. That is genuine when/how guidance. However it is delivered in dense metaphor ('the back booth is left out of that mix') and never covers when to prefer read_tab or my_replies over this feed.

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