exportRecords

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

Annotations already declare readOnly=true/destructive=false, and an output schema covers the return value, so the description adds the non-obvious behavior: a downloadable CSV artifact is produced rather than data returned inline, and it carries an explicit consent gate. It does not mention size/limit or performance characteristics of large exports, keeping it from a 5.

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?

Three sentences, each earning its place, with the gating condition front-loaded ahead of the alternative and the prerequisite. No filler or restatement of the name.

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?

For a 4-parameter export tool with full schema coverage, complete annotations, and an output schema, the description fills the remaining gaps agents need: when it is appropriate, what it replaces, and what to do first. Nothing required for correct invocation is missing.

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 100%, so all four parameters (limit, where, labels, orderBy) are already documented by the schema, which sets the baseline at 3. The description adds a useful cross-tool equivalence ('accepts the same labels/where/orderBy filters as findRecords') and a hint on sourcing field names, but says nothing about limit or filter syntax beyond that.

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 (export), resource (matching records) and concrete output artifact (a CSV file), which distinguishes it from findRecords and other read tools. An agent knows exactly what the call produces without opening a 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?

Gives both the when ('only when the user explicitly asks to export/download CSV') and the when-not with a named alternative ('for normal reading... use findRecords instead'), plus a prerequisite ('call findProperties first' before building a where filter). Nothing is left to inference.

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