gold_etsy_bulk_grade_shop

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

With no annotations, the description carries the full burden and delivers meaningful behavior: scope ('ENTIRE active shop up to 100 listings, one call'), ordering ('ranked worst-first'), output components ('per-listing fix lists + shop average'), and cost/access ('PAID ONLY PRO $29'). It does not explicitly state that no listings are modified, but 'grade' and 'fix lists' imply analysis rather than mutation.

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 essential behavior is front-loaded and the description is compact. 'POWER TOOL' is redundant marketing, but the rest of the sentence adds value, including the eRank comparison and BYOK/paid-only caveats.

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 one-parameter tool with no output schema, the description covers scope, ordering, output shape, and cost/access. It lacks an explicit no-modification guarantee and doesn't mention what happens when a shop has fewer or more than the limit, but these are minor for this complexity level.

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 schema already fully documents the only parameter ('1-100 default 50'), so coverage is 100%. The description adds no extra meaning about the limit beyond what the input schema provides, matching the baseline.

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 names a specific verb and resource: 'A-F grade your ENTIRE active shop' with concrete output ('ranked worst-first with per-listing fix lists + shop average'). This clearly distinguishes it from the likely single-listing sibling (gold_etsy_grade_listing) by targeting up to 100 listings in one call.

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 when to use it: when you need a shop-wide audit of active listings. However, it never explicitly names an alternative (e.g., a single-listing grader) or states when not to use it, so the routing decision is left partially to inference.

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