analytics_exports_list

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

With no annotations, the description carries the behavioral burden and discloses the 20-item cap, newest-first ordering, absence of download links, and the env fallback for org_id. It does not discuss permissions or pagination beyond the 20-newest limit, but the key behavioral constraints are present.

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 two sentences with no wasted text. The core listing behavior and the status-tool alternative are both front-loaded and easy to scan.

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 read-only list tool with optional parameters and no output schema, the description provides enough context: what is returned, ordering, cap, lack of download links, org_id source, and how to get links. Nothing critical is missing for correct invocation.

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 100%, so both org_id and app_project_id are already documented in the schema. The description reinforces the org_id source and env fallback but does not add meaning for app_project_id, so the baseline of 3 is appropriate.

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 a specific verb and resource: list the 20 newest analytics exports of an org, newest first, without download links. It also distinguishes the tool from analytics_export_status by explaining that status is where download links are obtained.

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?

It explicitly directs the agent to analytics_orgs_list or MCP_ANALYTICS_ORG_ID for the org_id, and names analytics_export_status as the alternative when a download link is needed. The selection condition between listing exports and checking export status is clear.

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