Shopdaten abrufen

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

With no annotations, the description carries the full transparency burden. It clearly states it is a read operation ('liest') and emphasizes 'pure facts directly from Etsy, no calculation,' indicating no transformation or side effects. However, it does not mention authentication requirements or error handling, which would add further clarity.

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 concise and well-structured: the first sentence lists the data returned, and the second adds a behavioral distinction ('no calculation'). No filler or redundancy; every sentence earns its place.

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 the tool's simplicity (no parameters, no output schema), the description provides a comprehensive list of returned fields, which gives the agent a clear expectation of the result. It lacks only an explicit return format or auth note, but these are not critical for such a simple read-only tool.

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 has zero parameters, so the schema coverage is trivially 100%. The description correctly omits any parameter details, and with no parameters to document, a baseline of 4 is appropriate.

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 a specific verb 'liest' (reads) with the resource 'Shop-Stammdaten' and enumerates exact data fields (name, title, announcement, etc.), making its purpose unmistakable. The phrase 'keine Berechnung' (no calculation) distinguishes it from the sibling etsy_analyze_shop.

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 the tool by listing the data it returns, but it does not explicitly state usage scenarios or name alternatives. The 'no calculation' note hints that etsy_analyze_shop might be for analysis, but no clear when-to-use or when-not-to-use guidance is provided.

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