conversations_list_prefs

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

With no annotations, the description bears full burden. It only states 'undocumented', hinting at instability but not disclosing behavioral traits like read-only nature, authentication needs, or default behavior given no parameters. The lack of parameter documentation is a significant gap.

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?

Extremely concise: a single sentence with no unnecessary words. It conveys the core function without extraneous information.

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?

Despite simplicity and presence of output schema, the description fails to explain the lack of parameters. The agent is left wondering how channel context is provided. The 'undocumented' label warns of unreliability, but the missing channel parameter makes the definition incomplete for correct invocation.

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 has zero parameters and 100% coverage, so baseline is 4. However, the description mentions 'per-channel', implying a channel parameter that does not exist, causing confusion. The description adds context but is inconsistent with the schema.

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 tool retrieves per-channel notification and mute preferences. The verb 'Get' and resource 'per-channel notification and mute prefs' are specific. However, the indication that the tool is undocumented is useful but does not directly aid purpose clarity. The empty input schema contradicts the 'per-channel' implication, slightly reducing clarity.

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 on when to use this tool versus alternatives like conversations_info or users_prefs_get. No conditions or prerequisites are mentioned. The description is purely functional without usage context.

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