altair_import_data

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

With no annotations, the description must disclose behavioral traits. It says 'Import/preview tabular data', but it is unclear whether this tool modifies state (imports) or only previews (read-only). The vague reference to 'ingestion actions' does not clarify safety, authentication, or side effects.

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 two sentences with no wasted words. The first sentence states the core function, and the second provides categorical context. It is efficiently structured and easy to parse.

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?

The description covers the main purpose and parameters for a simple tool without output schema or annotations. It lacks some context like whether the tool returns data or saves it, and what prerequisites exist (e.g., repository access). However, given the low complexity, it is largely complete.

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%, with clear descriptions for both csvFile and repositoryEntry. The tool description adds that these are two sources, but the schema already explains their meaning. The description does not add significant semantic value beyond 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?

The description clearly states the tool imports/previews tabular data from a repository entry or local CSV file. The mention of covering specific actions (1-2, 5-7, 9) provides some context, but it does not explicitly differentiate among siblings like altair_read_repository_entry, which may also handle repository data.

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?

The description indicates the tool is used for importing/previewing data from CSV or repository, but it does not specify when to choose this over alternatives, nor does it provide any exclusions or prerequisites. The agent is left to infer usage context.

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