spraay_sctp_po

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

Annotations already indicate non-read-only (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that it costs $0.02 per call, which is a useful behavioral trait. However, no other side effects or behaviors are disclosed, such as rate limits or failure modes.

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 concise with one sentence that front-loads the purpose. However, critical details are omitted, so it is not maximally effective.

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?

Despite a simple 3-parameter schema and the existence of an output schema, the description lacks important context: what the tool returns (e.g., PO ID), whether it is idempotent, and any validation rules. The description feels incomplete for a creation action.

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?

Schema coverage is 100% with descriptions for all three parameters, though they are minimal ('currency parameter', etc.). The description says to 'Provide the listed fields as typed arguments' but adds no further meaning beyond the schema, so it meets the baseline.

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 'Create purchase order' with a specific verb and resource. It distinguishes from sibling tools like spraay_sctp_po_by_id which retrieves an existing PO.

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 versus alternatives. There are no prerequisites mentioned, such as needing a supplier, and no comparison with related tools like spraay_sctp_invoice or spraay_sctp_pay.

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