HarvestAll

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

The description only states deprecation, which is a key behavioral trait. However, with no annotations, it lacks details about side effects, return values, or what happens when harvest is sent. The deprecation is useful but incomplete.

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?

Extremely concise: one sentence conveying deprecation and purpose. No wasted words, front-loaded with [DEPRECATED].

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 deprecated tool with one parameter and no output schema, the description is minimal. It doesn't explain what harvest means, how to use the storeId filter, or what to use instead. Lacks completeness for an agent to make informed decisions.

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 describes the storeId parameter with 100% coverage. The description adds no extra meaning beyond the schema. Baseline score of 3 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 explicitly states the tool is deprecated and sends harvest requests to all marketplaces. It distinguishes from siblings like HarvestAllV3, but could be more specific about what a harvest request entails.

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?

No guidance on when to use this tool vs alternatives (e.g., HarvestAllV3) or when not to use it. The deprecation warning implies it should not be used, but no alternative is suggested.

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