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. The description adds nothing beyond that – no mention of whether generation is synchronous, whether the PDF reflects the latest policy version, or any auth/premium gating. With annotations doing the heavy lifting, the description still leaves a behavioral gap.

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?

One short, front-loaded sentence with zero padding, which is good structurally. However, the brevity comes at the cost of under-specification rather than being earned conciseness.

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-value explanation is not required. Still, for an export tool the description should note the output format/layout source (e.g., company document styles, location PDF templates) or versioning behavior; none of that is present, leaving the agent with only the name to work from.

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 0% and the single parameter policyId has constraints (pattern, max length) documented only in the schema, not prose. The description never mentions what identifier to pass or where to obtain it, so it fails to compensate for the coverage gap even though there is only one parameter.

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 'Generate a policy PDF' essentially restates the tool name export_policy_pdf with a verb swap. It conveys the output format (PDF) and resource (policy) but does nothing to distinguish this from export_policy_word or export_sop_pdf, which share the same verb family.

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 when-to-use guidance, no prerequisites, and no mention of the obvious siblings (export_policy_word, export_sop_pdf). The agent must infer from the name alone that this is the PDF variant for policies rather than SOPs or Word exports.

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