pospal_list_product_purchases

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

The description provides no behavioral disclosure beyond the basic action. Since no annotations are provided, the description carries full burden for transparency. It fails to indicate whether this is a read-only operation, any side effects, required permissions, or response characteristics.

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 extremely concise at one sentence, which is good for conciseness, but it sacrifices necessary detail. It is front-loaded but lacks structure to convey useful context.

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 5 parameters, 2 required, and 0% schema coverage, the description is severely incomplete. It does not explain date range filtering, pagination behavior, or what information is returned. The existence of an output schema does not excuse the lack of context.

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 description mentions no parameters and provides no meaning beyond the schema. With 0% schema description coverage, the description should compensate but does not. The five parameters remain completely undocumented in natural language.

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 it lists purchase orders with pagination, which clearly identifies the verb and resource. There is no sibling tool with 'purchase' in name, so it is sufficiently distinctive. However, it lacks detail about what constitutes a purchase order in this context.

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 is provided on when to use this tool versus alternatives, nor any prerequisites or limitations. The description simply says 'pagination query purchase orders' without any usage context.

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