get_settings

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds value by enumerating which settings are returned (shipping_config, tax_config, etc.), but it does not disclose any other behavioral details such as output format or ordering, which are not needed given the simplicity.

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 a single, concise sentence that front-loads the purpose ('Get store settings') and follows with a colon-separated list of config types. There is no redundant or filler content.

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?

This is a simple getter with no parameters, no output schema, and a readOnlyHint annotation. The description lists the main settings it returns, which is sufficient for the agent to understand the tool's coverage. The sibling tools clarify that this is the read counterpart to update tools.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameters, and the schema is essentially empty. The description's mention of specific config sections provides context on what the tool returns, which is useful.

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 verb 'Get' and the resource 'store settings', followed by the specific config sections it retrieves. This makes the tool's purpose unambiguous and distinguishes it from sibling tools that perform updates (update_settings, update_store_config).

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 implies the tool is for reading store settings, and the presence of sibling tools like update_settings suggests a read-versus-write distinction, but it does not explicitly state when to use this tool over alternatives or provide exclusionary criteria.

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