conceptio_download_pdf

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false; the description resolves the most confusing part of that profile by clarifying that the write is to a local file path, and adds the real constraint that only open-access originals can be fetched. It stops short of covering overwrite behavior for an existing output file or failure modes on network errors.

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?

Two sentences, front-loaded with the action and resource, second sentence covering the accepted input forms. No filler or restated title matter.

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, the description adequately conveys the effect (a file written to the given local path) and the two accepted input forms. A brief note on what is returned (e.g., saved path or success confirmation) and overwrite behavior would close the remaining gap for a tool with openWorldHint=true.

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 both parameters (doc_id_or_url, output_path) are already documented in the schema, and the description roughly restates that an ID or URL is accepted. It adds the provenance hint that the ID comes from conceptio_search, but nothing about path semantics or ID format beyond the schema.

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?

States a specific verb (download) and resource (the original open-access PDF of a paper, standard, or book) plus the destination (a local file path). An agent can tell this apart from read-only siblings like conceptio_get_document, though the differentiation is implicit rather than stated.

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 when to use it by naming the input sources — a Conceptio document ID 'from conceptio_search' or a direct PDF URL — which hints at a search-then-download flow. It gives no explicit when-not conditions or alternatives, and doesn't say what to do if the paper is not open-access.

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