tokportal_create_comment_tasks

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

Beyond annotations that indicate mutation and non-idempotency, the description discloses partial-success semantics, per-task credit debit, no charge for rejected rows, account lock/revalidation, single-transaction commit, and idempotency replay behavior. This is rich behavioral detail that annotations alone do not provide.

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 front-loaded with the core purpose and then efficiently covers prerequisites, billing, transactionality, and idempotency in dense but purposeful sentences. Every sentence adds necessary operational information without 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?

For a complex batch mutation tool with no output schema, the description covers prerequisites, batch size, credit costs, partial success, idempotency, and a response field hint ('credits_charged'). It could more explicitly describe the response shape or partial-success structure, but it is largely complete for operational use.

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%, so the baseline is 3. The description adds meaningful operational semantics beyond the schema: credit cost per accepted task, requirement for Idempotency-Key, and the directive to read 'credits_charged' rather than calculating it. This supplements the parameter-level documentation effectively.

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 opens with 'Create comment tasks' and clearly states the scope: 'Creates one comment task or a partial-success batch of up to 200.' This provides a specific verb, resource, and batch capability, distinguishing it from sibling tools like list_comment_tasks, get_comment_task, and delete_comment_task.

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 provides strong usage context: prerequisites for the saved account, TokPortal Coverage requirements, credit costing, transactional behavior, and explicit Idempotency-Key guidance. It does not explicitly name alternative tools or when-not-to-use scenarios, but the operational context is clear and actionable.

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