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

Adds substantial behavior beyond annotations: re-import performs an upsert rather than duplicating, preserves existing status, and enforces a 1,000-row cap. 'Free' also communicates the cost profile, which is not captured anywhere in structured fields. The upsert-and-preserve semantics is exactly the kind of write behavior an agent cannot infer from idempotentHint alone.

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 short sentences, front-loaded with the core action and format, then the dedupe behavior, then the optional scoring. Nothing is redundant with the title or schema.

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 write tool with no output schema, the description covers input sources, limits, dedupe semantics, and cost, which is most of what an agent needs. It does not say what a successful import returns (counts of created vs. updated, row-level errors), a modest gap for a bulk mutation.

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 the baseline is 3, but the description adds real meaning on top: the 1,000-row limit is a constraint on the required `csv` parameter not present in the schema, and 'Pass criteria to pre-score them' explains the effect of `criteria` rather than just its shape. `source` and the auth parameters are left entirely to 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 and resource ('Import creator applications') plus the accepted input formats (CSV or plain-text export). It is clearly distinguishable from siblings like list_applications, review_applications, and update_application_status, so an agent can route correctly.

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 clear operating context — bulk import from form exports, up to 1,000 rows, with optional criteria pre-scoring. It does not explicitly say when to prefer this over per-applicant alternatives, but the bulk-vs-single distinction is strongly implied by 'up to 1,000 rows' and the export-source framing.

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