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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering safety and openness. The description adds that the PDF is fetched from a public https URL and warns that the call may count against the account's rate limit, providing useful context beyond annotations. It could have disclosed timeout or error behavior but is sufficient.

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 concise sentences: one detailing what metadata is returned and the source, and a second noting rate limit and the API endpoint. No wasted words; the purpose is front-loaded.

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 a single fully documented parameter and rich annotations, the description is largely complete. It covers the source (public https URL), returned fields, and rate limit warning, but does not mention potential errors for invalid URLs or output format details (though no output schema exists).

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 parameter is fully documented in the schema. The description adds that the URL must be public and https, reinforcing the constraint, but does not add much beyond that. Baseline is 3, but the extra 'public https' qualifier earns a 4.

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 (retrieves metadata) and resource (PDF downloaded from a public https URL) and lists the exact metadata fields returned. This clearly distinguishes it from siblings like craftmypdf_create_pdf or craftmypdf_merge_pdfs.

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 implies the tool is used when you need metadata about an external PDF, but does not explicitly state when to choose this over alternatives or any preconditions such as the URL must be public and https. Usage is only loosely implied.

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