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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description's 'Read-only' line is consistent with them. It adds context beyond annotations: results are newest-first, each row names its artifacts, and links in past results may be stale so check_task must be re-called for fresh ones. It does not discuss rate limits or page-size behavior beyond what the schema states.

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 tight sentences: purpose and ordering first, then use cases, then the hand-off to check_task, then safety. Every clause carries information, though the closing fragment 'Read-only.' is largely redundant with the readOnlyHint annotation.

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 no output schema, the description does enough to set expectations — newest-first ordering, artifact names per row, and that full results come from a separate call. Pagination and filtering semantics live in the well-covered input schema, so an agent has what it needs, though a brief note on what a row's fields look like would close the remaining 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 description coverage is 80%, so kind, limit, before and session_id are already documented in the schema and the description adds no syntax or format detail for them. It only touches the cursor concept indirectly via the check_task {job_id} reference, so the description does not meaningfully 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 with scope and ordering: 'List the jobs this account submitted, newest first', and enumerates the two job kinds with their creating tools (DAW conversions / convert_project, bounces / bounce_session). An agent can immediately distinguish this history-listing tool from doseedo_check_task, doseedo_convert_project, and doseedo_bounce_session.

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?

Gives three concrete situations that select this tool — finding an earlier result, checking what is still running, or resuming after a lost connection — and explicitly routes to doseedo_check_task {job_id} when the full result with fresh links is wanted. No alternative needs to be inferred.

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