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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently says 'NotOffered', which informs the agent that the tool will not provide orders, and adds that receipts/licence keys are external (Gumroad). It does not describe what actually happens on invocation (e.g., error or empty response), but the core behavior is disclosed.

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 a single concise sentence with no unnecessary words. However, its brevity comes at the cost of essential operational information; it is more of a status notice than a tool description, so it earns only a mid score.

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 that the tool is marked 'NotOffered', the description explains the basic situation and directs users to Gumroad. But it leaves the 'limit' parameter entirely unexplained, provides no output schema, and does not reference any sibling tool as an alternative, making it incomplete for an agent deciding how to proceed.

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 one parameter, 'limit', with no description and 0% schema description coverage. The description does not mention 'limit' at all, leaving the agent with no understanding of what this parameter controls or whether it is even accepted.

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 states 'Storefront: NotOffered' which indicates the tool is unavailable, and mentions Gumroad as the home of receipts and licence keys. However, it lacks a specific verb or action describing what the tool actually does when invoked, and it does not clearly distinguish itself from sibling tools like get_order_status.

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 hints that receipts and licence keys should be obtained from Gumroad rather than this tool, implying it should not be used for those purposes. It does not, however, specify when to use this tool versus any sibling alternative, nor does it state that the tool should simply not be called.

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