dnd_info

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It merely states 'retrieve' without confirming it is read-only or non-destructive. It omits auth requirements, error handling, and what happens when parameters are omitted (defaults to authed user).

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 (one sentence, 8 words). While brevity is good, the lack of essential details makes it under-specified. It earns a middle score for not wasting words but failing to cover necessary 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 having an output schema (which may explain return values), the description fails to mention what the output contains, how to specify a user, or that the tool defaults to the authenticated user. The low parameter coverage and missing usage context make it incomplete for an agent to invoke confidently.

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 description coverage is 0%, and the description adds no parameter-specific information. It does not clarify that 'user' expects a user ID or email, or that 'team_id' is optional. The meaning of parameters is completely left to the schema, which lacks descriptions.

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 'Retrieve' and clearly identifies the resource as 'a user's current Do Not Disturb status'. It effectively distinguishes the tool from sibling tools like dnd_team_info (team-level info) and mutation tools (dnd_end_dnd, dnd_set_snooze).

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 provides no guidance on when to use this tool versus alternatives (e.g., dnd_team_info for team status, or dnd_set_snooze for changing status). No context on prerequisites, supported user identification, or default behavior is given.

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