Get subscription export

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so "Reads account data" is largely redundant. The added value is the auth requirement disclosure — "OAuth integrations require subscriptions:read" — which is not present in the annotations or schema and tells an agent what credential scope is needed before calling.

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, front-loaded sentences with no padding. The opening sentence duplicates the title, which is minor waste, but the auth-scope note is placed prominently rather than buried.

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 read-only tool with full annotation coverage and a complete schema, this is close to adequate. However, no output schema exists and exports are typically asynchronous, so the description could have said whether this retrieves a finished export or polls status and what the export object contains; that lifecycle context is missing.

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%, with export_id, publication_id, and account all documented in the schema (including the pattern constraints and account resolution rules). The description adds nothing about the parameters, so the baseline of 3 applies.

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 first sentence, "Get subscription export," is essentially the title restated, so it is close to tautological. It does clarify the resource type (a subscription export, not a generic export) and implies retrieval of an existing object, but it never says it fetches a single export by publication_id/export_id and does nothing to distinguish it from the siblings create_export or list_exports.

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 statement of when to use this tool versus create_export or list_exports, and no prerequisites or conditions given. The OAuth scope line hints at an access constraint but is not usage guidance.

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