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

Annotations declare openWorldHint=true, readOnlyHint=false and destructiveHint=true, and the description adds genuinely non-derivable behavior: an x402 payment is required, the cost is $0.0015 per successful PDF, and the payment signature must be placed in _meta. That is exactly the kind of auth/billing context annotations cannot express.

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 most valuable content (payment requirement and signature placement) is buried after boilerplate 'calls the Actor and retrieves its output results' text that merely restates the name. It is not bloated, but it is not front-loaded around what the agent most needs to act 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?

An output schema exists, so return values need no explanation, and the description covers the payment gate, per-PDF pricing, and wait/polling semantics. Minor gaps remain, such as failure/refund behavior on unsuccessful PDFs, but nothing essential to correct invocation 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 description coverage is 100%, so the six documented parameters already carry their own semantics and the baseline would be 3. The description goes beyond the schema by disclosing a hidden, undocumented input channel (the required x402 payment signature in _meta), which is real added value for correct invocation.

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 the concrete operation: it calls the 'industrial_platform/pdf-text-intelligence' Actor and retrieves its output, and the embedded Actor description specifies the resource precisely (embedded PDF text, pages, metadata). An agent can distinguish it from generic siblings like get-dataset-items or get-actor-run, though the framing is boilerplate wrapper language rather than a direct verb+resource statement.

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?

No guidance on when to choose this tool over the sibling run/dataset tools, nor on prerequisites such as URL eligibility beyond what the schema already says. The only conditional information given is the polling hint in waitSecs, which is parameter-level, not tool-selection guidance.

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