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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing that the file is uploaded via RapidAPI to a NAS service, consumes plan allowance, is single-shot with no automatic retries, leaves originals untouched, and writes verified results as new local files. It also flags returned artifacts as untrusted data, a genuine prompt-injection warning.

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 purpose and limits, then prerequisites, network/cost behavior, and a safety note. Every sentence carries a distinct, actionable fact (size cap, consent, plan consumption, no retries, non-destructive output) with 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 still tells the agent what comes back (typed JSON or a CSV ZIP, saved as new local files) and covers cost, network egress, retry semantics, and data trustworthiness. Nothing needed to call this correctly 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?

Schema coverage is only 33% (only 'consent' is documented inline), but the description compensates: it explains the accepted file type and size ceiling for 'file' and the typed JSON vs CSV-ZIP outcomes for 'format', and restates the consent gate. It does not spell out accepted path syntax or whether 'file' may be a URL, leaving a small gap.

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 ('Export supported scalar tables from a local MDB/ACCDB snapshot') plus hard scope limits (40 MiB, typed JSON or CSV ZIP). It also names what it is not ('Does not migrate forms, macros, saved queries or linked data'), so an agent can separate it from any inspection/preview sibling without reading schemas.

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?

Clear preconditions and exclusions: local MDB/ACCDB snapshot, ≤40 MiB, consent:true, and an explicit when-not list (forms, macros, saved queries, linked data). It does not name an alternative tool or say what to do when the input is a remote/live database, so it stops short of full 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?

The annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by stating that no key, filesystem access, network request, or processing allowance is required, which goes beyond 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 two short sentences with no wasted wording. The purpose is front-loaded, and the operational caveat follows naturally.

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 informational tool with rich read-only annotations and no output schema, the description is largely complete. It says what will be described and what is not required, though it could clarify the return format or how subscription links are presented.

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?

This tool has zero parameters, so there are no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and the description introduces no parameter confusion.

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 verb, 'Describe', and concrete resources: four supported file tools, limitations, and subscription links. It clearly marks this as an informational capability tool rather than one of the sibling file-operation tools, though it does not name the four tools 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 description does not say when to call this tool versus the sibling file tools, nor does it give exclusions or alternatives. The note about not requiring a key, filesystem access, network request, or processing allowance is prerequisite information rather than usage routing.

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?

Goes well beyond the annotations: discloses the consumption of plan allowance, a single request with no automatic retries, that originals are preserved and results saved as new files, that other ZIP members must remain unchanged, that balanced mode mutates pixels, and that returned artifacts are untrusted data. These are exactly the behavioral facts an agent needs before invoking a non-idempotent remote mutation, and nothing contradicts 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?

Purpose and scope are front-loaded, and the subsequent sentences each add substantive constraint rather than filler. It is dense and runs long, but no sentence is redundant; a slightly tighter grouping of the consent/allowance caveats would make it a 5.

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 a mutation tool, no output schema, and only 25% schema description coverage, the description supplies cost, retry, side-effect, and safety-policy context well. What is not covered is the shape of the returned result beyond 'verified results saved as new local files' – e.g., what fields or paths come back – leaving a small gap for the agent.

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 25%, so the description must carry the load and it does: file is the selected asset passed through RapidAPI, budget_bytes is a complete-ZIP budget with an 8 MiB ceiling, mode's balanced setting changes pixels while lossless is implied safe, and consent:true is required. Each of the four parameters gains meaning beyond the raw 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?

States a specific verb (optimize), a specific resource (PNG/JPEG members of a local HTML5 ad ZIP), and a specific constraint (complete-ZIP byte budget up to 8 MiB). Nothing overlaps with the sibling tools (capabilities, access_extract, patterncopy_*, shelfrelay_preview), so an agent can select it unambiguously.

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?

Clear context for when to use it: shrinking image assets inside a ZIP to fit a byte budget, with the lossless vs. balanced trade-off spelled out and the note that visual review may be needed. It also warns that an over_budget result is legitimate, which prevents an agent from treating that as an error. It does not name any alternative tool or exclusion condition, so it falls 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?

Beyond the annotations, it discloses the 20 MiB limit, RapidAPI/NAS routing, plan allowance consumption, single request with no retries, original preservation, new-file result saving, and untrusted artifact handling. These are exactly the operational details an agent needs before invoking the 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?

The description is front-loaded with the core purpose and then layers on limits, consent, network behavior, side effects, and security cautions. It is dense but largely earns its length; a few points, such as 'supported-profile preflight,' are jargon-heavy and could be tighter.

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?

Given no output schema, the description covers most behavioral and safety-relevant context, including file preservation and new-file result saving. It could be more explicit about the returned artifact format or the exact metadata returned, but an agent has enough to call it correctly.

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 50%, and the description adds useful file constraints such as 'local supported PDF up to 20 MiB.' The consent parameter is already fully described in the schema, and the description adds little beyond repeating the consent requirement.

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 verb and resource: inspecting a local supported PDF for page/layer/form metadata. It explicitly distinguishes itself from the sibling action by saying 'without stamping it,' making the purpose clear without opening the 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?

It provides clear context as a supported-profile preflight and explicitly excludes independent visual certification. However, it does not explicitly name patterncopy_stamp or other siblings as the alternative when actual stamping is needed.

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 only give readOnly/openWorld/idempotent/destructive flags; the description adds the substantive behavior an agent needs: consent:true is mandatory, the file and options traverse RapidAPI to a NAS service, the call consumes the subscribed plan allowance, there are no automatic retries, originals are preserved and verified output is written as new local files. It also warns that returned artifacts contain untrusted data, which is valuable for an openWorldHint 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?

The core action is front-loaded in the first sentence, followed by operational constraints and safety notes. Every sentence carries information, though the middle sentence about layers and geometry plus review is slightly dense and the block could be separated into tighter clauses rather than one long run-on.

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 6-parameter, open-world mutation with no output schema, the description covers consent gating, transfer path, plan consumption, retry behavior, file preservation and where results land. It leaves out the numeric bounds/defaults and the exact shape of the returned artifact, which is the main remaining gap.

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 only 17% (just the consent field), so the description carries extra burden. It partly compensates by naming the documented options (corner/position, font size, margin) and constraining input ('one line', 'left-to-right', 'PDF up to 20 MiB'), but it omits the actual ranges and defaults (margin 6-72, font_size 6-14) and never explains the 'text' or 'file' parameter format beyond size.

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 ('Add one line of supported left-to-right text to every page of a supported PDF') with concrete limits (20 MiB, corner/font/margin options). It is clearly distinct from the sibling patterncopy_inspect, but it never names a sibling or explicitly contrasts with one, so it stops 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?

Usage context is implied via 'reserve clear space on every page and review the result' and 'One request, no automatic retries', which tells the agent to call deliberately. However, there is no explicit when-to-use/when-not or routing to alternatives such as patterncopy_inspect for inspection or patterncopy for other operations.

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 are supplemented with details the schema cannot express: data transits through RapidAPI to a NAS service, consumes plan allowance, exactly one request with no automatic retries, originals preserved and verified results written as new local files, plus a prompt-injection warning that returned artifacts are untrusted. These are consistent with openWorldHint=true, idempotentHint=false, and destructiveHint=false. The cost and no-retry disclosures are exactly what an agent needs before committing a paid mutation-adjacent call.

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 purpose and return value, then constraints, then the trust warning. Almost every clause carries load-bearing information (cost, retries, preservation). It is long for one paragraph and could be trimmed slightly, but nothing is 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 two-parameter but high-consequence remote call with no output schema, the description covers consent, network path, billing, retry behavior, on-disk persistence, and output trust level. What is missing is a sense of the artifact's shape (how many updates, how to validate success vs partial failure) and any size limits on the request beyond the schema's 4096-char string bound.

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 50%; the consent parameter is fully documented in the schema and reinforced by 'Requires consent:true'. The description adds useful content hints for 'file' (it carries the records/policy envelope and optional previous_xml state) and that it is a local file, but never states whether the value is a path or inline JSON, which is the one ambiguity an agent must resolve to call this correctly. Baseline 3 for partial coverage.

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 concrete input (a local JSON request carrying the ShelfRelay records/policy envelope plus optional previous_xml state) and a concrete output (a review artifact with typed ONIX updates scoped to the physical-ISBN/single-authority profile). That is far more specific than the bare name 'preview' and separates it from the batch/optimize siblings. It stops short of explicitly contrasting with a named sibling, so 4 rather than 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?

'Requires consent:true' and 'Does not apply changes to WooCommerce or fetch referenced covers' set a clear boundary for when this tool applies and what it will not do. The preview-then-apply framing is implied by 'review artifact'. Missing: an explicit pointer to which sibling or follow-up call performs the apply step.

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