Get Storefront Setup Instructions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the tool gets instructions, but does not clarify whether it is a safe read-only operation, what accounts/scopes are involved, or what the returned instructions look like. The term 'custom' is ambiguous and unexplored.

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 short sentence, which is concise and front-loaded. However, it under-specifies by omitting what 'custom' means or what the instructions contain, making it minimally informative despite its brevity.

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 its simplicity (no params, no annotations, no output schema), the description should still explain what the setup instructions cover, whether they are generic or store-specific, and how to use them. The current text leaves these elements open-ended and is insufficient for an agent to fully understand the tool's value.

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 has zero parameters, and schema coverage is 100% (vacuous). The baseline for no parameters is 4, and the description adds no conflicting or necessary parameter information. No additional semantic explanation is needed.

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's function: 'Get custom storefront setup instructions.' The verb 'get' and resource 'storefront setup instructions' specify the purpose. It distinguishes from sibling ecommerce tools that manage storefronts, though it doesn't explicitly contrast with them.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or what to do after receiving instructions. This leaves the agent to infer based solely on the tool name.

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