getDeliveryDateSetting

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

Annotations already declare readOnly and idempotent. Description adds key behavioral context: 'setting is common to entire shop,' 'no arguments required,' and 'returns current values.' While not exhaustive, it supplements annotations well.

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?

Four sentences, front-loaded with purpose and key information. Every sentence serves a purpose: what, scope, arguments, usage, sibling reference. No 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 simplicity and existing annotations, the description covers purpose, scope, usage, and alternatives. It mentions return fields in parentheses but lacks explicit return structure details. Still adequate for selection and invocation.

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?

Input schema has a dummy parameter with description 'Not used.' The description reinforces 'no arguments required,' clarifying that the dummy parameter is irrelevant. Schema coverage is 100%, so description adds marginal extra clarity.

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 it gets delivery date/time settings, defines the scope (shop-wide, not per delivery method), and distinguishes from sibling tool getDeliveries by directing users there for delivery methods.

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?

Explicit usage scenarios: referencing before presenting options in cart, or matching with order data. Also notes no arguments required and provides alternative getDeliveries for delivery method listings.

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