users_prefs_get

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

No annotations are provided, and the description does not disclose behavioral traits beyond the implied read operation. It fails to mention side effects, access requirements, or any limitations. For an undocumented legacy tool, more transparency is expected.

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 extremely concise at just three words plus a parenthetical. It is front-loaded with the essential purpose and includes a key qualifier (legacy) in minimal space.

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?

Given the lack of parameters and presence of an output schema, the description is minimally adequate. However, it does not explain what user preferences are, why it's undocumented, or whether there is a newer alternative. The completeness is average.

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 input schema has zero parameters, so there is nothing to explain. The description does not elaborate on what preferences are returned, but since schema coverage is 100% (vacuously), the baseline is met. No added value beyond stating the resource name.

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 'Get user preferences' clearly states the action (Get) and the resource (user preferences). The addition of 'legacy undocumented' provides specific context that distinguishes it from potential siblings like users_prefs_set or team_prefs_get.

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?

The description mentions 'legacy undocumented' but does not explicitly state when to use this tool versus alternatives. It gives no guidance on whether this should be avoided or what to use instead, leaving the agent without clear usage context.

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