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

The description adds no behavioral information beyond the annotations. It doesn't disclose that the tool runs in dry-run mode by default (from the schema) or describe the mapping process or side effects. With annotations lacking such specifics, the agent is left uninformed about important execution behavior.

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?

The description is a single, focused sentence with no filler, front-loading the core action and target.

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?

Despite having an output schema and substantial annotations, the description is too sparse for a 9-parameter tool. It omits the crucial dry-run default behavior and the meaning of 'map', making the description inadequate for a complete understanding of the tool.

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?

The schema provides descriptions for 89% of parameters, so the baseline is 3. The description does not add any parameter-specific meaning, such as explaining the relationship between csv_text and file_url, but the schema already covers the basics.

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 clearly states the tool imports and maps a clinic price CSV into Toofi pricing configuration, using specific verbs and resources. It differentiates from sibling tools like generate_price_estimate or get_agent_billing_quote, which deal with pricing outputs rather than CSV imports.

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 is provided on when to use this tool versus alternatives. The description doesn't mention scenarios, prerequisites, or exclusions, leaving the agent without context for choosing it over other pricing-related tools.

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