probely_list_sequences

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

No annotations exist, so the description must bear full transparency burden. It identifies the operation as a read-only list, but does not disclose pagination behavior despite the 'page' parameter, nor does it mention permissions or side effects. Minimal but acceptable for a simple list operation.

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 efficient sentence that conveys the core purpose without unnecessary words. It is appropriately front-loaded and earns its place.

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?

Despite an output schema existing, the description lacks completeness. It does not specify pagination behavior (even though a 'page' parameter exists), nor does it provide usage context relative to sibling tools. For a tool with two parameters and no schema descriptions, the description is insufficient.

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 fails to explain the 'targetId' or 'page' parameters beyond their names. The description adds no meaning to the input schema, leaving the agent without guidance on how to use these parameters.

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 verb 'List' and the resource 'login sequences', with scope 'for a target'. It distinguishes from sibling list tools (e.g., credentials, findings) and specific sequence tools (e.g., get_sequence).

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 implies listing all sequences for a target, but does not explicitly state when to use this tool vs alternatives like probely_get_sequence (single sequence) or probely_list_credentials. No when-not or alternative guidance is provided.

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