Create Business Hours

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

Annotations already provide readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by mentioning 'via the Metadata API' and the integration context with other Salesforce components, which goes beyond the structured annotations. It doesn't detail permissions or edge cases, so it's not a 5.

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 exactly two sentences, front-loaded with the primary action and method, and contains no filler. Every sentence adds relevant information about what the tool does and why it's used.

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 comprehensive input schema and annotations, the description adequately covers the tool's purpose and business context. It explains the relationship with SLA-related features but doesn't address return values (no output schema exists) or explicitly mention the optional isDefault parameter, though the schema covers it.

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 100%, so all five parameters (name, timeZone, days, isActive, isDefault) are already documented. The description loosely references 'working hours for each day, time zone, and active/inactive days' but adds no new parameter-level detail beyond what the schema provides, earning the baseline 3.

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 Business Hours in Salesforce via the Metadata API,' providing a specific verb, resource, and method. This distinguishes it from siblings like sf_create_holiday or sf_create_entitlement_process, which target different resources.

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 explains that Business Hours are used with Entitlement Processes, Escalation Rules, and Holidays to calculate SLA milestones, giving clear context on when this tool is relevant. However, it doesn't explicitly state when not to use it or name alternatives, so it falls short of a 5.

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