marketo_get_bulk_export_file

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

With no annotations, the description must disclose behavior. It warns that 'Large files may be clipped in MCP response', which is useful. However, it omits details on error conditions (e.g., non-Completed status) and response handling (e.g., whether the content is inline or a URL). Basic transparency, but gaps remain.

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 short sentences, each contributing essential information. The purpose is stated first, followed by format, then warning. No redundancy or filler.

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 simple one-parameter tool with no output schema, the description covers the main behavior: download completes, returns CSV/TSV, and clipping possibility. It lacks details on exact response format (e.g., inline binary or base64) and error messages, but is largely complete for typical 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?

The single parameter exportId has a description in the input schema that is repeated in the tool description ('must be in Completed status'). Since schema description coverage is 100%, the baseline is 3. The description adds no additional meaning beyond what the schema already provides.

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 verb 'Download', the resource 'file from a completed bulk export job', and the output format 'CSV/TSV content'. It is specific and distinguishes from sibling tools like marketo_create_bulk_export_leads or marketo_get_bulk_export_status.

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 specifies a clear precondition: 'Only works when job status is Completed.' This guides the agent to check status before invoking. It does not explicitly name alternatives, but the context implies it is the final step in the bulk export workflow.

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