get_export

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states that it retrieves metadata, but does not disclose the impact of the 'download' parameter (e.g., whether a download URL is included by default, or any error behavior). It fails to clarify what happens when the ID does not exist or whether additional permissions are required.

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 a single, concise sentence that directly states the tool's purpose. It is front-loaded and contains no unnecessary words, earning its place.

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 tool has no output schema, so the description should explain return values. It only says 'metadata' without specifying fields or the difference when 'download' is true. The interaction between the two parameters is not clarified, leaving the description incomplete for a tool with two parameters and no structured output.

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 description coverage is 50%, with only 'download' having a description. The tool description adds no meaning to either parameter; it does not explain 'id' or elaborate on the 'download' behavior beyond the schema. Since the schema already covers half, the description needed to compensate for the other half but does not.

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's function: 'Get export metadata by ID.' It specifies the resource (export metadata) and the identifier (ID), making it easy to distinguish from list or create export tools. However, it does not explicitly differentiate from other get_* tools, though the resource is self-evident.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, the need for an existing export ID, or comparison to list_exports/create_export. It offers no contextual framework for selection.

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