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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description's one real contribution is disclosing that sample values are synthetic and safe to expose, which is meaningful context an agent wouldn't otherwise know; it stops short of saying whether the catalog is static or workspace-dependent.

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 front-loaded sentence with no filler. It is efficient but arguably too terse for the gaps it leaves around usage and return shape.

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?

No output schema exists, so the description must carry the return-value burden; it says the result contains field names and sample values but not the shape, whether field types or required flags are included, or how fields map to template columns. Adequate for a simple read, but incomplete for actually building a template from the result.

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 coverage is 0% and the single required parameter is an empty object wrapper whose purpose the description never explains. Baseline would be 4 for a no-argument tool, but the unexplained required 'input' envelope leaves a real ambiguity about whether the caller must supply an empty object.

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?

Specific verb ('Read') plus resource ('supported CSV source fields') plus the extra payload ('safe synthetic sample values'), which distinguishes it from the sibling list_export_templates that returns templates rather than fields. It just doesn't name that sibling, so differentiation is inferred 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?

No guidance on when to call this versus list_export_templates, create_export_template, or update_export_template, and no mention of the workflow it supports (discovering valid source field names before building a template). The use case is only implied by the tool name.

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