admin-get-all-preferences

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the operation is admin-scoped and 'retrieve' implies a read-only action, but it omits details about potential large data volume, pagination, or whether it returns all preferences across all users. No rate limits or side effects are mentioned.

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 a single short sentence, 'Admin: retrieve all user preferences.' with no extraneous words or repetition. It is entirely front-loaded and easy to parse.

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 has no parameters and no output schema, so the description is the only source of information. It fails to clarify what 'all user preferences' encompasses (e.g., all users vs. one user) and does not describe the response structure, leaving significant ambiguity for an agent.

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, which per the rubric receives a baseline score of 4. The description adds no parameter information because the schema is already complete with an empty properties object.

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 the action ('retrieve') and resource ('all user preferences'), with an 'Admin:' prefix indicating administrative scope. However, it does not explicitly distinguish this from sibling tools like 'admin-get-user-preferences', leaving minor ambiguity about whether 'all' means all users' preferences or all preferences for a single user.

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?

No guidance is provided on when to use this tool versus alternatives such as 'admin-get-user-preferences' or 'get-my-preferences'. The 'Admin:' prefix hints at an administrative context but does not explain the appropriate use case or exclusions.

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