marketplace_pull

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

No annotations are provided, so the description carries the burden. It discloses spool directory defaults and the file-processing mechanism (*.eml, X-Marketplace-Kind header), which adds useful context. However, it does not state whether pulling consumes or deletes messages, whether it is idempotent, or any side effects – leaving ambiguity about the operation's impact.

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, front-loaded with the core purpose, and each detail about defaults and processing earns its place. No fluff or redundancy.

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 (one optional parameter, output schema present), the description covers the core behavior, spool location, and file format. It lacks explicit side-effect disclosure (e.g., whether messages are removed), which would make it more complete, but the output schema likely covers return values, so no explanation there is needed.

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 has 0% coverage, but the description fully explains the only parameter (spool_dir) by specifying the default resolution ('env ACP_INBOX or ./spool/executor'). This gives clear meaning and behavior beyond the bare schema definition.

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 clearly states the tool's function: 'Pull new marketplace listings from the inbound mesh spool' – a specific verb and resource. It is immediately distinguishable from sibling tools like publish, search, and outbox by focusing on inbound consumption.

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 context is clear: this tool retrieves new marketplace listings from a spool directory, with defaults explained. It doesn't explicitly mention when not to use it or name alternatives, but the purpose is unambiguous enough for an agent to select it for consuming inbound messages.

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