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

The description discloses important behavior beyond the annotations: the operation is an upsert ('create or update') and that the handle is auto-generated from the display name when omitted. It does not mention whether omitted fields are preserved or reset, but the provided behavioral details are meaningful.

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 two concise sentences with no filler. The primary action is front-loaded, and the most important optional behavior is stated succinctly.

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?

The description is adequate for identifying the tool and key behavior, but it leaves gaps: it does not state what happens to omitted fields during an update, and with no output schema it does not indicate what the tool returns. For a 7-parameter upsert tool, a bit more operational detail would improve completeness.

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 coverage is high at 86%, so the schema already documents most parameters. The description adds extra semantic value by explaining handle auto-generation behavior, which is not fully captured in the schema description.

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 identifies the action as creating or updating a seller storefront, which is more informative than the title alone. It also distinguishes this tool from the many sibling update_* tools by naming the specific resource and its 'nestuge-style page' nature.

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 gives clear context: this tool is for creating or updating a seller storefront. It does not explicitly name alternatives like get_storefront or state when not to use it, but the action and resource are clear enough that an agent can infer the intended use.

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