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

Annotations already set readOnlyHint=false, destructiveHint=false, and openWorldHint=true, and the description adds useful behavior beyond that: it returns the same attachmentId a chat upload would mint, it stages the text, it is free and consumes no AI credits, and the content must come from a user-chosen file. No annotation contradiction is present.

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 longer than average but every sentence earns its place: purpose, host-specific context, routing to the sibling, chat exclusion, safety warning, and cost. The key purpose and warning are front-loaded before the cost detail.

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 three-parameter staging tool with an output schema and full parameter coverage, the description covers the entire call flow: where the file text comes from, what is returned, which sibling to call next, and when to avoid the tool. 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% and the parameter descriptions are already explicit, so the baseline is 3. The description adds contextual color by tying csvContent to 'the user's file in the browser' and by explaining the returned attachmentId, but it does not add new parameter-level syntax 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 opening sentence names a specific verb and resource: 'Stage CSV TEXT so it can be imported as a dataset.' It also distinguishes itself from the sibling import_attachment_as_dataset by explaining it produces an attachmentId that should be passed to that tool, and clarifies it is not a generic upload by warning not to invent content.

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 explicitly says when to use it ('MCP Apps hosts... no file transport'), when not to use it ('In chat you never need this'), and names the next step ('Pass that id straight to import_attachment_as_dataset'). It also gives a strong negative guideline: 'Do NOT invent CSV content to call this with.'

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