token_bowl_chat_admin_get_all_users

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: it is admin-only, returns sensitive information, and raises AuthenticationError when the caller lacks privileges. It omits pagination, volume limits, or what "sensitive information" concretely includes, but the auth and data-sensitivity profile is well covered.

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?

Front-loads the critical [ADMIN ONLY] constraint and uses clear Returns/Raises sections. The admin requirement is stated three times ([ADMIN ONLY], "Requires admin privileges", and the Raises clause), a minor redundancy, but the structure is otherwise tight and easy to scan.

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?

An output schema exists, so return values need not be detailed, and the description still gives a brief Returns note. For a zero-param, admin-gated read tool, the auth prerequisite and data-sensitivity warning cover what an agent needs before calling.

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 clarify and the baseline is 4. Nothing is misleading about the absence of parameters.

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 complete profiles for all users in the system") and the [ADMIN ONLY] tag plus "all users" sets it apart from the single-user sibling token_bowl_chat_admin_get_user and the non-admin token_bowl_chat_get_users. However, it never explicitly names or contrasts those siblings, so an agent must infer the distinction.

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 view full details for all registered users including sensitive information" gives implied usage context and the admin prerequisite, but offers no explicit when-not guidance and does not name alternatives (e.g. admin_get_user for a single record or get_users for public data). Adequate but leaves routing to inference.

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