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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so safety framing is covered. The description adds genuine runtime context beyond that: the monitor re-runs periodically and produces a new/removed/modified diff. It does not disclose what is returned at creation or any permissions required.

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 that states the action and the resulting behavior with no filler. Every clause (recurring, every N days, diff of new/removed/modified) carries 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 4-parameter creation tool with no output schema and 0% schema description coverage, the description leaves gaps: the meaning of 'name', the job-vs-pipeline exclusivity, and what the call returns are all unaddressed. It is adequate on behavior but thin on invocation detail.

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 0% across 4 parameters, so the description carries the full burden. It accounts for 'job or pipeline' (source_job_id / source_pipeline_id) and 'every N days' (frequency_days), but says nothing about the required 'name', the 1-90 day bound, or whether the two source parameters are mutually exclusive.

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 names a specific action (create a recurring monitor) and resource, and explains the resulting behavior: re-running a job/pipeline every N days and diffing results. It implicitly separates itself from one-shot siblings like create_scrap_job or create_enrichment_job, though it never names an alternative.

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?

Usage is only implied: 'turn a finished job or pipeline into recurring monitoring' suggests the precondition that a job/pipeline already exists and has run. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as list_monitors or create_pipeline.

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