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 elsewhere. The description still earns credit by disclosing the payload of each entry -- what each action takes, what it makes, and its credit price -- which tells the agent this is a metadata catalog rather than an executor. Return format and size are left to the output schema, which exists.

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 sentence, front-loaded with the verb and resource, with the per-entry contents appended in a compact parenthetical clause. Nothing is wasted and nothing important is buried.

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 catalog tool with an output schema and full annotation coverage, this is nearly sufficient -- the agent knows it gets a list of actions with inputs, outputs, and cost. The only real gap is the missing cue about when in a workflow to consult it, which is a usage concern rather than a completeness one.

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 schema has zero properties, so the baseline is 4 and there is nothing to document. The description correctly implies the call takes no arguments by describing it as a pure enumeration. No contradiction or omission.

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 a specific verb (list) plus the resource (every action FynePDF can run on a file) and even enumerates what each entry contains: inputs, outputs, and API-credit price. That is far more precise than the title alone. It stops short of 5 because it never distinguishes itself from siblings such as app_ready or the many action-style tools (compress_pdf, ocr_pdf, etc.), which an agent could easily confuse with a catalog call.

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 statement of when to call this (e.g. before invoking an action to discover its name or cost) or when not to. The usage is only weakly implied by the word 'list'. Naming no alternative and giving no precondition makes routing to this tool guesswork.

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