firestarter_seller_analytics

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description aligns by saying 'View.' Beyond annotations, it discloses the specific data points returned (revenue, order count, AOV, daily breakdown), adding behavioral context about the tool's output without contradicting the annotations.

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 sentences with no wasted words. The first sentence states the purpose and scope, and the second provides usage guidance. It is front-loaded and perfectly concise.

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?

For a zero-parameter, read-only analytics tool, the description fully covers the returned data (revenue, order count, AOV, daily breakdown) and usage context. No output schema exists, but the description adequately compensates by specifying what the tool provides.

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 description coverage is 100%, so there is no need for parameter explanations. The baseline of 4 applies because the description does not need to compensate for missing parameter documentation.

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 uses the specific verb 'View' and clearly defines the resource: seller revenue and order analytics. It lists exact metrics (total revenue, order count, average order value, 30-day daily breakdown), which precisely distinguishes it from sibling tools like firestarter_seller_orders that deal with individual orders.

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 explicitly states 'Use when a seller asks about their performance, earnings, or sales trends,' providing clear context. It does not name exclusions or alternative tools, but the context is sufficient for an agent to decide when to invoke it.

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