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

No annotations are supplied, so the description must carry the behavioral load. 'List' implies a non-mutating read, but nothing is said about ordering, truncation beyond the default limit, or whether the result set is paginated — gaps that matter for a listing tool with no safety hints.

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 compact clauses with the primary action front-loaded and the downstream-reuse hint second. No filler or restated title text.

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?

With three optional params, no annotations, and no output schema, the description should say more about the returned list shape (fields available per job, ordering, truncation). Naming the cap_* id format and follow-up tools covers part of the need, but the return characteristics remain unspecified.

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 appId, limit, and notification_message are already documented. The description only echoes the appId filter ('optional appId filter') and adds nothing about limit semantics or the notification_message parameter, so it does not exceed the schema baseline.

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?

States a specific verb and resource ('List existing capture jobs'), scopes it to 'your workspace', and identifies the returned ID format (cap_*). The reference to get_capture_job as a follow-up makes clear this is the discovery/lookup tool rather than the single-job fetch.

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 frames usage as a way to obtain captureJobIds that are then 'reused' with get_capture_job, patch_checklist, browser_control, so the agent knows the downstream workflow. It does not state when NOT to use it (e.g., when the id is already known), so it stops short of full alternative guidance.

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