get_store_settings

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's closing 'Read-only' adds nothing. What it does contribute is scoping context — that the read covers fulfillment workflow, guardrail and payment configuration for a single store — which is genuinely useful, but it discloses no auth requirements, rate limits, or behavior when settings are unset.

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?

One front-loaded sentence with the verb first, and the long enumeration of settings all earns its place by telling the agent what the read returns. The trailing '[#3b3cd0]' artifact is stray noise that slightly undercuts an otherwise tight structure.

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?

With no output schema, the description usefully enumerates the returned setting categories (fulfillment_mode with its enum values, approval_authority, guardrails, auto-reconcile, payments), which compensates for the missing return documentation. Parameters are fully covered by the schema, so the only gap is the absence of usage routing.

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% for both parameters (workspace and store_uuid, the latter cross-referencing list_my_stores), so the schema carries the burden. The description adds no syntax, format, or workspace-scoping nuance beyond that, making the baseline 3 correct.

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?

States a specific verb ('Read') and resource ('a store's fulfillment workflow + notification settings') and enumerates the exact setting families exposed (fulfillment_mode, approval_authority, hold guardrails, auto-reconcile, payment settings). An agent can distinguish this read-side tool from the sibling update_store_settings without opening either schema.

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?

There is no when-to-use guidance, no prerequisites, and no explicit routing to sibling tools such as update_store_settings or check_setup_readiness. The field enumeration hints at utility but the description never states the condition that should select this tool.

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