get_notification_preferences

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

No annotations provided. Description only states it reads preferences without detailing side effects, permissions, or rate limits. A read operation is inherently non-destructive, but the description does not explicitly confirm this or address other behavioral traits.

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?

Single sentence that efficiently conveys the purpose and scope. Could be slightly more structured with bullet points for readability, but it is not overly verbose.

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?

No output schema, and description does not specify the return format. It lists the categories of preferences, providing some context, but lacks details like data types or structure. Adequate for a simple read tool with no parameters.

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?

Input schema has zero parameters, so no parameter documentation needed. Description does not add parameter info, which is acceptable since there are none. The 100% schema coverage with no params means the description cannot add value here, baseline is 4.

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 uses a specific verb 'Read' and resource 'notification preferences', listing concrete sub-categories (channels, cadence, toggles, locale, timezone). It clearly distinguishes from sibling 'set_notification_preferences' as the read counterpart.

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 explicit guidance on when to use versus set_notification_preferences or other tools. The read/write distinction is implied but not stated. Does not mention prerequisites or alternatives.

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