list_crawl_jobs_route

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

Annotations already carry readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only the temporal scope ('ongoing and recent'), which is useful but thin, and says nothing about result ordering, pagination limits, or whether all users' jobs are visible.

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?

A single lean sentence with no wasted words and the resource front-loaded. The title-case phrasing and the vague 'Created By A User' clause are the only minor blemishes.

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?

For a read-only, 3-parameter list tool with full schema coverage and no output schema, the description is minimally adequate. It leaves unclear whose crawl jobs are returned and how ongoing vs recent are defined, which an agent must infer.

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 100%, with cursor, page_size (max 100, default 30) and include_job_ids all documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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?

Specific verb 'List' with resource 'Crawl Jobs' and a scope qualifier 'ongoing and recent'. An agent can distinguish it from get_crawl_job_route (single item) and cancel/create_crawl_job_route by inference, though the description never names those siblings. The trailing phrase 'Created By A User' is ambiguous about which user, slightly muddying the scope.

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 offers no when-to-use guidance, no mention of alternatives such as get_crawl_job_route for a single job, and no note about when to prefer this listing. Usage is only implied by the verb 'List'.

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