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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description still adds genuine context beyond them: the webhook path is masked and credentials are returned only as prefixes, which tells the agent the payload is deliberately redacted. It does not discuss auth behavior beyond what the schema says.

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 front-loaded sentence listing the returned fields, plus a compact REST route reference in parentheses. No filler and no repetition of the schema.

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 simple read tool with full annotations, full schema coverage, and no output schema, the description usefully summarizes the return payload and its redaction behavior. Only the missing guidance on when to choose this over get_run, get_deliveries, or list_jobs keeps it from being complete.

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%, and the job_id format (job_<ULID> from create_job) and the optional management_token fallback are fully documented in the schema. The description adds no parameter-level information, 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?

The description enumerates exactly what is returned for a single job (settings, status, next_run_at, run_count, credential prefixes) and the phrase 'of one job' implicitly separates it from list_jobs. It stops short of an explicit retrieval verb or naming a sibling, so it is clear but not maximally differentiated.

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: nothing says to call this after create_job, or to prefer get_run/get_deliveries for execution history or list_jobs for enumeration. The agent must infer the context from the sibling names alone.

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