get_crawl_job_route

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds nothing beyond that - no note on error behavior for a missing job id, no indication of what 'details' includes, no auth or rate-limit context. It neither contradicts nor enriches the annotations.

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 front-loaded phrase with zero redundancy or filler. It is concise to a fault - nothing extraneous, though also nothing substantive beyond the heading.

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?

The tool is simple (one required parameter, read-only, fully annotated), so the description carries a light burden and the annotations plus schema cover safety and input semantics. However, with no output schema, an agent gets no hint of what 'details' contains (status? config? errors?), and there is no differentiation from the list/cancel siblings.

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% - crawl_job_id is documented in the schema as 'The id of the crawl job to retrieve'. With only one well-documented parameter, the baseline of 3 applies; the description contributes no additional meaning about id format or provenance.

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 'Get Crawl Job Details' is essentially the tool name/title restated with the words reordered; it names no scope, return shape, or distinguishing feature. It does not differentiate this tool from siblings such as list_crawl_jobs_route (listing) or cancel_crawl_job_route (cancellation). An agent can guess it fetches one job, but only from the identifier in the name, not from the description.

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?

There is no when-to-use guidance and no mention of alternatives. With list_crawl_jobs_route and cancel_crawl_job_route in the sibling set, the description should at minimum state that this retrieves a single job by id rather than enumerating or cancelling jobs. Nothing is offered.

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