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

Beyond the readOnlyHint and idempotentHint annotations, the description adds important behavior: it returns a request to make yourself rather than data, includes whether the publisher enabled downloads, and explains the workspace key requirement. It accurately aligns with the non-destructive, read-only annotations.

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 concise sentences front-load the exact return value, then provide an example, a key behavioral distinction, and an auth note. Every sentence adds necessary information without redundancy or padding.

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?

Given the single parameter, no output schema, and rich annotations, the description is complete: it covers what is returned, how to authenticate, the non-streaming behavior, and when to prefer this tool. An agent has everything needed to invoke it correctly.

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 has no descriptions for the single table_id parameter, but the description compensates with context and an example. It makes clear the parameter identifies the table whose Parquet snapshot download instructions are being requested, which is sufficient for one obvious UUID parameter.

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 names a specific verb and resource: it returns the exact URL, HTTP method, and header for downloading a table's immutable Parquet snapshot. It also distinguishes the tool from query_table by explicitly saying this is preferred over paging a whole table, and clarifies this is not a streaming data tool.

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?

It explicitly directs the agent to prefer this tool over query_table for snapshot downloads, and explains that bytes are never streamed through MCP. It also states the authentication prerequisite (mr_use_ workspace key) and that the result includes how to obtain one, giving clear guidance for correct use.

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