passgage_export_data

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Export data'. It does not mention whether the operation is read-only, if it returns a file or URL, requires authentication, or has side effects like generating a server-side file.

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 very concise, consisting of one sentence with no fluff. However, 'Export data' largely restates the tool name, and the value is mainly in listing formats. It's efficient but slightly redundant.

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 tool has nested parameters (filters, date_range) and no output schema, the description should explain the output format (e.g., file download, URL) and how filters/date_range affect the result. It provides none of that, leaving the agent with significant gaps.

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 input schema already documents all parameters (resource, format, filters, date_range) with descriptions and enums, and schema coverage is high. The description adds no parameter detail beyond what the schema provides, so it meets the baseline with no additional value.

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 states the verb 'Export' and specifies output formats (CSV, JSON, Excel), making the core action clear. However, 'data' is vague and doesn't enumerate the resource types; the schema provides this, but the description alone is not fully specific.

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?

No guidance is provided on when to use this tool versus list/get tools, nor any alternatives, prerequisites, or context. The description is a single declarative sentence with no usage advice.

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