probely_update_sequence

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

No annotations are provided, so the description carries full burden. It indicates 'update' which implies mutation, but fails to disclose important behavioral traits such as whether the update overwrites or merges fields, authentication requirements, or any side effects. The description only offers a best-practice tip, not behavioral specifics.

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 contains two sentences plus an example JSON. It is moderately concise, but the example is useful. The first sentence is clear; the second sentence and example add value but could be condensed slightly. Still, it is not overly verbose.

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 parameters, 2 required, no annotations), the description lacks completeness. It does not explain the update behavior (e.g., whether it is a partial update or full replacement), prerequisites (e.g., sequence must exist), or what the output contains (despite an output schema existing). The custom_field_mappings guidance is helpful, but many other aspects are missing.

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 0%, so the description must compensate. It only provides a detailed explanation for the custom_field_mappings parameter, including its JSON array format and an example. The other five parameters (targetId, sequenceId, name, content, enabled) are not described at all, leaving significant gaps.

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 states 'Update a login sequence', which clearly indicates the verb (update) and resource (login sequence). It is not a tautology. However, it does not explicitly differentiate from sibling tools like probely_create_sequence or probely_configure_sequence_login, but the name itself clarifies the action.

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 advises using custom_field_mappings and credential URIs for sensitive values, implying best practices. However, it does not explicitly state when to use this tool versus alternatives (e.g., creating a new sequence or configuring sequence login). Usage context is implied, not explicit.

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