List images

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds some non-obvious context — provider scopes, locks, and credits apply — which goes beyond the structured fields. But it never specifies how pagination behaves or what the credit/lock constraints concretely mean, leaving the value shallow.

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 short and front-loads the endpoint, with no filler sentences. But the three fragments are essentially a path plus two boilerplate clauses, so brevity comes at the cost of substance rather than being efficient information delivery.

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 and one of two parameters undocumented, the description should carry more weight than it does. It omits return format, pagination behavior, and what the mentioned locks/credits actually restrict, leaving an agent short of what it needs to call the tool confidently.

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%: account is documented in-schema, but page has no description at all. The tool description says nothing about pagination, page limits, or the account scoping parameter, so it fails to compensate for the undocumented parameter.

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 anchors the tool to an endpoint, "GET /v5/images", which conveys a read/list operation on the images resource. However, it offers no differentiation from siblings like get_image (single image) or list_image_templates (a different resource), and "Current Bannerbear V5 operation" adds nothing an agent can act on. Purpose is identifiable but essentially restates the tool name.

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 and no mention of alternatives such as get_image or list_image_templates. "Read operation" is a restatement rather than a routing cue, so the agent must infer context from the name alone.

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