Create Data Extract

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

Annotations already indicate destructiveHint=true. The description adds that the tool returns an 'initial status', hinting at asynchronous processing. However, it does not disclose potential side effects, required permissions, or behavior under failure beyond what annotations provide.

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 sentence, concise and to the point. It front-loads the key action and output. However, it is slightly under-specified, which prevents a perfect score.

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 that the tool has an object parameter and an output schema, the description provides minimal context. It does not explain what extract_data should contain, potential errors, or prerequisites. The presence of siblings like list_data_extracts and get_data_extract implies a workflow, but the description lacks completeness.

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 0%, and the description does not explain the parameters (extract_data and request_id). Since the description adds no meaning beyond the raw schema, it fails to compensate for the missing schema descriptions.

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 action ('Request a new data extract'), the resource ('data extract'), and the purpose ('for bulk reporting'). It also specifies the return value (extract ID and initial status), distinguishing it from siblings like get_data_extract and list_data_extracts.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description implies creation but does not mention when not to use it or suggest sibling tools like get_data_extract for retrieval. Sibling differentiation is only implicit through naming.

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