Check assets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'Read operation' is largely redundant. It does add non-structured context that provider scopes, locks, and credits apply, which is genuinely useful for a billable operation, but it stops short of explaining what the operation returns or how the lock/credit behavior manifests.

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 fragments, front-loaded with the route, with no filler. However 'Current Bannerbear V5 operation' is boilerplate that consumes space without informing the agent, and the terse form leaves the core meaning unstated rather than being efficiently 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 tool with a nested payload object, no output schema, and no required parameters, the description omits the single most important fact: what a 'check' evaluates and what the caller should expect. With no output schema the description is not obliged to detail return values, but it must at least characterize the operation, which 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?

Schema description coverage is 100%, so the account, payload, and payload_file parameters are already documented, including the mutual-exclusivity rule and the 1 MiB non-symlink constraint. The description adds nothing beyond identifying the endpoint, making the baseline 3 appropriate.

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 gives only the HTTP route 'POST /v5/assets/check' and the tautological title 'Check assets' — it never states what the operation actually does (e.g., verify asset existence against content hashes). An agent cannot distinguish it semantically from siblings like list_assets or get_asset, which also read assets.

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, no prerequisites, and no named alternative among the many asset siblings. The agent must infer that 'check' is different from 'get' or 'list' entirely on its own.

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