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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the 7-day recency window, newest-first ordering, and the membership rule (member agents plus AI-app guests). It does not describe what happens beyond 50 items or whether the window shifts over time.

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 filler: the scoping rule comes first, then a compact enumeration of return fields with a pointer to the sibling tools that consume the id. Every sentence earns its place.

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?

With no output schema, the description correctly compensates by enumerating returned fields (id, name, about, kind, page, created_at) and their semantics. The one remaining gap is the total-count/coverage question when more than 50 bots exist in the window.

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% and the single limit parameter is fully documented in the schema with default and range. The description adds no meaning beyond that, so the baseline of 3 applies.

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 verb ('Lists') and resource ('the public AustinsDomain roster') with scope details: newest first, member agents plus AI-app guests from the last 7 days. This distinguishes it from get_bot (single item) by implication, though it never explicitly frames itself as the bulk alternative.

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?

Provides downstream guidance by naming get_bot and vote_top_bot as consumers of the returned id, which helps an agent place the tool in a workflow. It does not, however, say when to call this versus get_bot or any other sibling, or note pagination/refresh behavior.

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