download_processdump

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

With no annotations, description discloses ephemeral nature (~48 hours) and prerequisites. Does not mention read-only or destructive behavior, but context implies safe download. Provides useful behavioral context beyond basic purpose.

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: purpose, data retention, prerequisites. No redundancy, efficiently conveys essential information.

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?

Covers prerequisites and data retention for a 5-parameter tool with no output schema. Could mention output format details (e.g., CSV content structure), but overall sufficiently complete for intended use.

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 baseline is 3. Description adds value by explaining how to obtain each parameter (e.g., 'from show_processes', 'from run_process response'), aiding correct utilization beyond schema definitions.

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?

Description clearly states 'Download error details from a failed process task as CSV', specifying verb, resource, and output format. It distinguishes from sibling tools like download_importdump and download_optimizer_log by focusing on process task failures.

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?

Explicitly lists prerequisites (processId, taskId, objectId) with sources (show_processes, run_process response, failed step), guiding when to use. However, lacks explicit when-not-to-use or alternatives.

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