list_shop_sections

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered structurally. The description adds nothing beyond that: no indication of whether sections are returned in order, whether an empty list is possible, or what a "section" contains.

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?

It is a single fragment with zero wasted words, but the brevity reflects under-specification rather than disciplined editing. There is nothing to front-load because almost no content exists.

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 tool is simple (no params, no output schema), so full completeness is achievable in a sentence or two, yet the description never states that it returns a collection of section records or any constraints. An agent learns only that "sections" belong to "your shop".

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 takes zero parameters, so the schema imposes no burden on the description and the baseline of 4 applies. There is no parameter meaning the description could or should have added.

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?

"Your shop sections." is a noun phrase that essentially restates the tool name (list_shop_sections); it implies a listing of sections but names no verb and gives no scope. It does not distinguish itself from siblings such as get_my_shop or list_listings beyond the noun "sections".

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 prerequisite (e.g. shop authentication), and no mention of when to prefer this over get_my_shop or list_listings. The agent must infer usage entirely from the tool name.

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