probely_create_sequence

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

No annotations are provided, so the description carries the full burden. It discloses that creating a sequence does NOT automatically enable it, and explains credential linking behavior. However, it does not mention idempotency or whether overwriting is possible.

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 thorough but structured: first sentence states purpose, then content requirement, important note, then credential instructions. It is front-loaded but could be more concise; however, every sentence adds value.

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 the complexity (6 params, 3 required), missing annotations, and existing output schema, the description covers creation process and post-condition well. It lacks details on return values or errors, but output schema likely fills that gap.

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 0%, so description must compensate. It explains 'content' as a JSON string of the sequence steps array, and provides example formats for credential mappings. It does not explain 'targetId' or 'name', but those are common and partially inferred. Adds significant value over bare 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?

The description clearly states 'Create a login sequence', which is a specific verb+resource. It distinguishes from siblings by mentioning the need to call probely_configure_sequence_login after creation, contrasting with other credential-related tools.

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?

Explicitly provides when-to-use (credential vs inline values) and a required post-step (call probely_configure_sequence_login). It also gives alternative approaches (use existing credential or inline).

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