isw_create_paycode

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

With no annotations, the description carries the full burden. It only discloses the confirm requirement, but does not explain side effects, idempotency, failure conditions, or what happens if confirm is false.

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 sentence with no wasted words. It is concise but could benefit from additional structure or details.

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?

The description is severely lacking for a write operation with 8 parameters and no output schema. It does not explain what a paycode is, expected return, or lifecycle, leaving the agent with insufficient 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?

Schema description coverage is only 38%; many parameters lack descriptions. The description adds no parameter semantics beyond the schema, merely restating the confirm requirement.

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 action 'Create a cardless withdrawal paycode,' specifying the verb and resource. It is distinguishable from siblings like isw_get_paycode_status and isw_deactivate_paycode, but does not explicitly differentiate from isw_create_bulk_paycodes.

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 description mentions that confirm must be true, which is a usage requirement, but provides no guidance on when to use this tool versus alternatives (e.g., bulk paycode creation) or prerequisites.

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