manage-focused-inbox

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

Annotations declare readOnlyHint=false and destructiveHint=false, indicating state modification without destruction. The description adds behavioral detail: list shows overrides, set creates/updates, delete removes. This aligns with annotations and provides clear action semantics.

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?

Three concise sentences that immediately state the purpose then enumerate actions. No filler or redundant information; every sentence adds value.

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 description covers all actions and their parameter dependencies. No output schema exists, but return values are not critical for a management tool. Minor omission: behavior on non-existent delete is not stated, but overall sufficient.

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?

All 5 parameters are documented in the schema (100% coverage). The description adds value by specifying default values (action=list, classifyAs='focused') and clarifying required fields per action (emailAddress required for set/delete). This enhances understanding beyond 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?

Description clearly states it manages Focused Inbox overrides with three specific actions (list, set, delete). The resource is distinct from all sibling tools, which include unrelated operations like send-email or manage-category.

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?

Description explains each action and its default behavior (action=list default, classifyAs default). However, it does not explicitly state when to avoid using this tool or suggest alternatives, but the uniqueness of the resource makes usage implicit.

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