Create Holiday

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

Annotations already handle safety traits (readOnly=false, destructive=false, idempotent=true). The description adds the 'via the Metadata API' detail and explains the relationship to Business Hours, offering useful behavioral context beyond what annotations provide.

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 long, directly states the core purpose, and is well-structured with the action first. Every sentence adds value without unnecessary fluff.

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?

Given the tool's moderate complexity (8 parameters, all documented), the description provides enough context about purpose and usage. Annotations fill in safety traits, and no output schema is needed for a create operation. An agent can confidently select and invoke this tool.

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 input schema covers all 8 parameters with full descriptions (100% coverage), so the baseline is 3. The description's mention of one-time/recurring holidays and optional Business Hours association largely restates schema information without adding significant new meaning.

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 begins with a clear action ('Creates a Holiday record in Salesforce via the Metadata API') and specifies the resource and purpose (exclude days from SLA calculations). It distinguishes itself from siblings like sf_create_business_hours by focusing on holiday records specifically.

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 clear context by explaining that holidays are used with Business Hours to exclude days from SLA calculations, making the use case evident. It does not explicitly mention alternatives, but no direct alternative exists among siblings, so the context suffices.

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