create-outlook-category

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

Annotations indicate this is destructive (creates data) and open-world. The description adds context beyond annotations: it explains the unique displayName constraint and color mapping, which are important for correct usage. No contradictions with annotations.

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 two sentences plus a brief tip, all front-loaded with essential information. Every sentence provides value, and there is no redundancy or unnecessary text.

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?

For a create tool with nested parameters and no output schema, the description covers the key behavioral aspects (uniqueness, color mapping, case sensitivity) and provides enough guidance for an agent to invoke it correctly. It could be improved by mentioning the return value (created object), but it is still fairly complete.

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 description adds value beyond the schema by explaining the color enum maps to named colors (e.g., preset0 = red) and that displayName must be unique and case-sensitive. Schema coverage is 67%, and the description effectively compensates for the missing details in the schema's property 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 clearly states the tool creates an outlookCategory object in the user's master list of categories. The verb 'Create' and resource 'outlookCategory' are specific, and it distinguishes from sibling tools like list-outlook-categories.

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 a tip explaining the required body structure and notes that category names are case-sensitive when applied. While it does not explicitly state when to use or not use this tool versus alternatives, the context of creating a category is clear and sufficient for an agent.

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