token_bowl_chat_get_users

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

No annotations are provided, so the description carries the full burden. It does disclose the return shape and a filtering nuance ('non-viewer users'), which is real behavioral context, but omits whether the operation is read-only, any auth/permission requirements, and pagination behavior for a list endpoint.

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?

Purpose is front-loaded, followed by usage and a return-field list. The bulleted return enumeration is somewhat verbose given an output schema already exists, but it is well-organized and mostly 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?

For a zero-parameter read tool with an output schema, the description covers purpose, use case, and returned fields. The lack of annotations leaves minor gaps (read-only nature, pagination), but complexity is low and coverage is otherwise solid.

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 nothing for the description to disambiguate beyond the schema; baseline 4 applies. No parameter-level detail is needed or expected here.

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 and resource ('Get a list of all registered Token Bowl Chat users') and notes a scoping detail ('non-viewer users'). However, it does not distinguish itself from near-identical siblings like token_bowl_chat_get_online_users or token_bowl_chat_admin_get_all_users, which an agent could easily confuse with this one.

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?

'Use this to discover all users in the system' implies a discovery use case but offers no when-not guidance and names no alternatives, despite several overlapping siblings (get_online_users, admin_get_all_users, get_user). Usage is only implied, not directed.

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