card_bulk_create

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

No annotations provided; description discloses SCA polling, default wait, fallback, and token reuse. Lacks details on idempotency or partial failures, but covers key behavioral traits.

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?

Two sentences, no wasted words. Front-loaded with purpose, then behavior. Efficient.

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?

Covers main behavior and SCA flow. No output schema, but response is implied (success or pending). Could mention error handling for partial failures, but adequate for agent 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% but description adds meaning: explains wait's role (polling control), sca_session_token for binding, and cards limit. Context beyond schema.

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?

Clear verb+resource+constraint: 'Bulk create cards (up to 50).' Distinct from sibling card_create (single card).

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?

Explains SCA handling, polling behavior, and fallback to pending response with guidance on sca_session_show and sca_session_token. Does not explicitly contrast with card_create but context implies for bulk use.

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