items_export

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

With no annotations provided, the description carries the full disclosure burden; it clearly states the operation returns the full inventory as a CSV string, which covers the main behavior. It does not explicitly confirm that no mutation occurs or mention payload-size caveats, but 'export' plus a no-parameter signature makes the read-only intent reasonably transparent.

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 tight sentence with no filler, and it front-loads the verb, resource, and output format. Every word earns its place for a parameterless tool.

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 zero-parameter tool without an output schema, stating both the resource ('full inventory') and the return shape ('CSV string') gives an agent enough to invoke it correctly. It could be more complete by naming a preferred alternative or exactly which fields the CSV includes, but the core contract is sufficient.

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 zero properties and 100% coverage, so there are no parameter semantics for the description to clarify. The zero-parameter baseline of 4 applies, and the description correctly emphasizes the output rather than arguments.

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 ('Export'), a clear resource ('the full inventory'), and a concrete output format ('CSV string'), so the tool's function is immediately identifiable. This phrasing also sets it apart from list/detail siblings like items_list and items_get, which do not describe CSV-format bulk export.

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?

There is no explicit guidance about when to choose this tool over alternatives, and no sibling is mentioned for comparison. The intended use case is only implied by the name and description, leaving the agent to infer that items_export is for bulk CSV output while items_list/items_get handle item retrieval.

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