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

Annotations already declare it is not read-only, not idempotent and not destructive, so the safety profile is partly covered. The description adds that the result is a link to the PDF, which is useful, but it never explains the side effect implied by readOnlyHint=false (e.g. whether a PDF file is persisted, whether repeated calls produce different links given idempotentHint=false) or any permission requirements. Additional behavioral context beyond the annotations is thin.

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, no filler, with the primary trigger stated first, the return value second, and the scope restriction last. Every clause earns its place.

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 the description need not explain the return payload, and the artifact-type scope is fully covered. The only shortfall is the unexplained non-idempotent, non-read-only behavior of the export operation, which leaves a minor gap for an agent deciding whether re-invoking is safe.

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?

There is a single parameter at 100% schema description coverage, and the schema already tells the agent that artifactId comes from search_artifacts or create_document. The description adds no format or sourcing detail beyond that, so the baseline 3 applies.

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?

Names a specific verb (export) and resource (a Xenition document as PDF), and explicitly carves out the artifact types it does not cover (slides, sheets, notes). An agent can distinguish it from siblings like get_artifact or edit_artifact without opening any schema.

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?

Front-loads the trigger condition (user wants a document as PDF to download, print or attach) and gives an explicit exclusion plus the alternative route for other artifact types (open them in Xenition to export). Both when-to-use and when-not-to-use are stated.

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