OutSend

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true). The description adds genuinely new context beyond them: the operation is asynchronous and returns a new job id, which is important for a job-creating tool with no output schema.

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?

One front-loaded sentence carries the verb, the async nature, the capability list, and the return value with no filler. The trailing 'etc.' is slightly vague but minor.

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 an async job-creation tool with three parameters and no output schema, the description covers the essentials (prerequisite, async, return id) but omits guidance on retrieving results via get_job/get_job_results and does not explain the full enrichment enum.

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 coverage is 67%, and the description only names a subset of the 15 enum values (emails, reviews, socials, techstack, verify_emails) while ignoring email_mode and source_job_id semantics. It adds some flavor but does not compensate for the remaining coverage gap, so 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 ('Enrich the results of a finished job') and enumerates the enrichment capabilities, which distinguishes it from create_scrap_job and create_pipeline. It does not explicitly name the sibling it differs from, keeping it short of a 5.

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 'results of a finished job' implies the prerequisite (a source job with status=done, confirmed in the schema), but there is no explicit when-to-use guidance or routing among the sibling job-creation tools.

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

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.

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false. The description adds real value beyond that: chains are linear, each block feeds the next, edge keys must be 'from'/'to' rather than source/target, and the call returns a pipeline id plus initial job ids. It doesn't discuss failure/partial-creation semantics, so not a 5.

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?

Front-loaded with the core action, then constraints, then the example. The example block is large but earns its place given the nested, free-form definition object. Minor density but no padding.

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 nested, open-world create operation with no output schema, the definition covers the shape of input, the key naming gotcha, the return values, and where to find the authoritative schema. An agent has everything needed to attempt a valid call.

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 coverage is only 50% and the nested definition object is largely unspecified, so the description compensates with a concrete worked example showing node id/type/config and edge structure. It also reinforces the from/to key convention already hinted at in the schema. It stops short of enumerating the optional 'name' parameter's role.

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 — 'Create AND start a multi-step pipeline' — with an inline example of the chaining concept, and it is clearly distinguishable from siblings like create_scrap_job or create_enrichment_job because it targets multi-step chains rather than a single job.

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?

It routes the agent to get_pipeline_schema for valid block types and config fields, which is explicit sibling delegation. It never states when NOT to use it versus a single-job creator such as create_scrap_job, so context is clear but exclusions are absent.

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

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, openWorld=true. The description adds genuinely non-structured context: the job is async, returns the job id immediately, and runs in the background until status=done. It omits concurrency/rate limits or auth requirements, so not a 5.

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 tight sentences with the core action and async contract front-loaded; nothing is padded. It is terse to the point of omitting needed parameter detail, but structurally clean.

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 7-parameter creation tool with 14% schema coverage and no output schema, the description is too thin: it leaves most parameter behavior and the required queries/zones distinction undocumented, so an agent cannot reliably construct a call from this alone.

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 coverage is only 14%, so the description should compensate, yet it only explains stop_at ("caps the number of unique places"). The six other parameters — zones, queries, scrap_mode, max_per_phone, extra_columns, and even the country default — carry no meaning in the description, and scrap_mode's enum values are unexplained.

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?

"Launch a Google Maps extraction (async)" gives a specific verb (launch) and resource (Google Maps extraction), clearly distinguishing it from create_enrichment_job, create_monitor, and create_pipeline by domain. It stops short of explicitly naming sibling alternatives, hence not a 5.

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 points to estimate_scrap before running, nor to get_job/get_job_results for polling. The mention of status=done only implicitly hints at a follow-up call, leaving routing between siblings to inference.

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

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

The readOnlyHint annotation already establishes that nothing is mutated, and 'WITHOUT launching it' reinforces this. The description adds genuinely useful context by defining the EF unit (one full-France scrape per query type), which helps interpret the result, but it says nothing about auth, rate limits, or how the estimate is derived.

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?

Two tight sentences, front-loaded with the core action and the key non-side-effect guarantee, followed by the unit definition. No filler.

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?

With no output schema, the description partially compensates by stating what is returned (cost in EF and volume). Combined with 80% schema coverage this is nearly complete, though it could say more about what drives the cost figure.

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 80%, so the schema already carries most parameter meaning, including the zones, queries, country, and stop_at semantics. The description adds no parameter-level detail such as which parameters most affect the estimate or how scrap_mode changes cost, 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 (estimate) and resource (cost and volume of a Google Maps extraction), and explicitly distinguishes itself from an actual run with 'WITHOUT launching it'. This separates it cleanly from the sibling create_scrap_job, which does the real extraction.

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?

'WITHOUT launching it' clearly frames this as a pre-flight/dry-run check, implying it should be called before committing to create_scrap_job. It gives clear context but never names the alternative tool or states an explicit exclusion, so it stops short of a 5.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the cursor/pagination behavior, which is real value, but omits ordering (newest first?), retention window, and whether events are filtered by account scope or polling frequency.

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?

Two compact sentences with no filler; the core purpose is front-loaded and the pagination rule is tacked on as a practical afterthought. Every clause earns its place.

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 no-required-param, read-only feed with no output schema, the description covers the essentials, but an agent still lacks guidance on result shape (beyond the event-name examples) and the semantics of 'limit'/'types'. Adequate but with clear gaps.

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 three parameters, so the description must carry the load. It explains since_id well and the event-type examples hint at what 'types' accepts, but 'limit' (max 100) and the exact accepted values for 'types' remain undocumented.

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 resource ('Account event feed') with concrete example event names (job.completed, pipeline.completed, veille.run_completed), which lets an agent recognize it as an event stream distinct from the job/pipeline CRUD siblings. It does not explicitly name a sibling it differs from, so it falls short of a 5.

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?

Gives operational guidance for pagination ('since_id takes the last_id of the previous call'), which is genuinely useful for iterating the feed. However, it never states when to use this versus alternatives like list_jobs or get_job, nor when not to use it, so usage is only implied.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully discloses the return content (status, counters, download URL), but says nothing about job lifecycle semantics — e.g. whether a job must be finished before a download URL is meaningful, or whether polling is expected.

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 short sentence with zero filler, front-loading the fields returned. It is a noun fragment rather than a full sentence, but nothing is wasted.

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, single-parameter lookup with no output schema, the description partially covers the return content but omits the job lifecycle context (finished vs running, polling) that an agent needs to use the status/download URL correctly. Annotations carry the safety profile, so the gap is moderate rather than severe.

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% and the single required parameter job_id has no schema description. The description never mentions the parameter, so it fails to compensate for the coverage gap, even though the parameter's meaning is largely inferable from its name.

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 the resource (a job) and enumerates the specific fields returned — status, counters, and download URL — which implicitly distinguishes it from get_job_results and list_jobs. It is clear but does not state an explicit verb or call out the sibling it differs from.

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 guidance on when to call this versus list_jobs or get_job_results, no mention of whether it should be polled until a job completes, and no prerequisites. The agent must infer usage entirely from the tool name and sibling names.

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

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

Annotations already declare a safe read-only, closed-world operation, so the bar is lower. The description still adds real behavior: a hard 50-row preview cap, offset-based pagination, and the existence of a CSV URL for the full export rather than truncated rows.

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 dense sentence that front-loads the preview semantics and appends the secondary details (count, CSV URL). Every clause carries information, though the '+' concatenation style is slightly compressed.

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?

With no output schema, the description does the work of describing the return payload (rows, total count, CSV export URL). Only the failure behavior for an unfinished job is left unstated.

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 coverage is 0%, so the description must carry the parameter burden and largely does: it documents the 50-row cap tied to 'limit' and the pagination mechanism tied to 'offset'. job_id is self-evident from the name.

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+resource ('Preview of a finished job's rows') and clarifies the payload: rows, total count, CSV URL. It implicitly distinguishes from get_job (metadata) and the create_* siblings, though it never names an alternative explicitly.

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 'finished job' implies this should only be called after completion, and 'paginate with offset' tells the agent how to iterate. However, it names no alternative tool and gives no guidance on what to do while a job is still running.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the payload is a contract consisting of block types, config schema, and chaining rules, but says nothing about caching, size, freshness, or whether pipelines must exist first.

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 with a colon-delimited inventory of contents; every clause earns its place and nothing is repeated from the title.

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?

With no output schema, the description must describe the return payload, and it names the three components an agent needs. It is close to complete for a zero-parameter introspection tool, though it could note that the result should be consulted before invoking create_pipeline.

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?

The tool takes zero parameters and the schema is trivially covered, so the baseline of 4 applies. There is nothing parameter-wise for the description to compensate for.

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 noun-resource ('Machine contract for building pipelines') and enumerates exactly what it returns: valid block types, per-block config schema, and chaining rules. It also ties itself to the sibling create_pipeline, so an agent can place it relative to the write tool without opening any schema.

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: mentioning that the rules are 'accepted by create_pipeline' suggests calling this before create_pipeline, but there is no explicit when-to-use, when-not, or named alternative. Adequate inference, no explicit routing guidance.

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

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

readOnlyHint=true and openWorldHint=false already establish this as a safe, non-open-world read, so the bar is low. The description usefully adds that results are ordered newest first, but omits pagination behavior, default result count, and what 'recent' means, which matter for a list tool.

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 short fragment with the ordering constraint front-loaded and no filler. It is efficient, though the terseness borders on under-specification rather than tight communication.

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?

With no output schema, no annotation detail beyond safety hints, and an undocumented limit parameter, the description leaves an agent without the pagination/default-count information needed to call this list tool predictably. It is too thin for the tool's surface.

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?

The lone parameter 'limit' has 0% schema description coverage, so the description must carry its meaning, but it says nothing about the limit, its allowed range (1-50), or a default. It mentions 'recent' without defining the window, leaving the retrieval size entirely undocumented.

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 fragment identifies the resource (the account's jobs) and its ordering (newest first), so an agent can guess it retrieves a job list. But there is no verb and no differentiation from siblings get_job, get_job_results, or list_pipelines, which are equally plausible for a job-related need.

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 gives no indication of when to call this versus get_job (single job) or get_job_results (results of one job). No prerequisites, no conditions, no exclusions are stated.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral caveat not present in the annotations: the coming_soon status blocks launching, and the catalog is scoped to capabilities ('what each one needs and produces').

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?

Two short sentences, zero filler, with the resource identity front-loaded and the usability caveat second. Every clause 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 zero-parameter read-only listing with no output schema, the description covers what is returned (module capabilities and requirements) and the one status caveat an agent needs to act correctly. Nothing material is missing.

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?

The tool takes zero parameters, so the baseline of 4 applies. Nothing in the description conflicts with the empty schema, and no parameter explanation is needed.

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 states a specific resource ('outsend data modules') and what the listing conveys ('what each one needs and produces'), which separates it from siblings like list_pipelines, list_monitors, and list_jobs. The verb is only implied by 'Catalog of' rather than stated outright, but the resource 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?

It gives an actionable constraint for downstream use ('modules listed as coming_soon cannot be launched yet'), which implies this tool is the discovery step before creating enrichment/scrap/pipeline jobs. However, it never explicitly says when to call this versus the other list_* siblings or what the preconditions are.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of pagination, ordering, scope of "recurring," or whether inactive monitors are included.

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?

It is a single short fragment with zero waste, but it is terse to the point of under-specification rather than efficient communication. Brevity here reflects missing content, not disciplined trimming.

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 no-param read-only list tool with annotations covering safety, the definition is minimally adequate. With no output schema, however, it should say something about what a monitor entry contains or how results are returned, and it does not.

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?

The tool takes zero parameters, so there is nothing for the description to explain; baseline 4 applies. The empty schema is fully consistent with the account-scoped framing.

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 phrase "The account's recurring monitors" names the resource but supplies no verb, so the listing action is only implied. It is distinguishable from siblings by resource name (monitors vs jobs/pipelines/modules), but the definition never states plainly that it returns the list.

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 indication of when to call this versus list_jobs, list_pipelines, or list_modules, nor any prerequisite or filtering guidance. The agent must infer usage entirely from the bare resource noun.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that returned pipelines carry status, which is useful payload context, but says nothing about pagination, ordering, or result volume.

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 terse sentence with the resource front-loaded and no filler. It is efficient, though bordering on under-specified rather than merely concise.

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 zero-parameter list tool with no output schema and annotations covering safety, the description is minimally adequate: it states the resource and that status is included. It omits any hint of ordering, pagination, or what a pipeline entry contains, which an agent would need for downstream use.

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?

The tool takes zero parameters, so the baseline is 4 per the rubric. There is nothing for the description to clarify beyond the empty schema.

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 the resource (the account's pipelines) and the payload content (with status), so an agent can tell it is a read/list operation on pipelines. It does not explicitly contrast itself with get_pipeline_schema or create_pipeline, but the resource and implied verb are 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?

There is no guidance on when to call this versus siblings like get_pipeline_schema or list_jobs, nor any mention of prerequisites or account scoping. The agent must infer usage entirely from the name.

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