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

Beyond the annotations (non-readonly, non-idempotent, non-destructive), the description discloses two things the annotations do not: the run is recorded in run history like a scheduled run, and the call requires the database:write scope. That auth/scope note is genuinely useful for a mutation tool. It stops short of saying what happens on a missing job name or whether concurrent firings are allowed.

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?

Three short sentences, zero filler, with the core action front-loaded and the scope requirement last as a trailing constraint. Nothing could be cut without losing information.

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 four-parameter mutation with full schema coverage and no output schema, the definition covers action, side effect (logged run), and required scope. The remaining gap is the return value — whether the agent gets a run id or operation handle to poll via schedule.runs — which is not stated.

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% — every parameter including its defaulting behavior (branch defaults to production, project_id/org_id default to session context) is already documented in the schema. The description adds nothing parameter-specific beyond the implicit job name, so the baseline 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?

States a specific verb and resource — 'Run a job once now, outside its timer' — which makes clear this triggers a job immediately rather than creating, updating, or listing schedules. It does not explicitly name the sibling it displaces (schedule.runs, schedule.create), but the purpose is unambiguous.

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 phrase 'outside its timer' implies the use case: trigger an existing job now instead of waiting for its schedule. There is no explicit when-not guidance and no mention of preconditions such as the job needing to already exist, so the agent must infer the boundary with schedule.runs and schedule.create.

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