panelica_migrations_get_v1_migration_sites_export

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

Annotations already cover read-only, idempotent, and non-destructive behavior; the description adds the useful auth requirement (`migrations:read`) and confirms the HTTP method. It does not describe response details, but the annotation coverage lowers the burden here.

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 extremely compact and front-loaded: purpose first, then endpoint, category, required scope, and read-only nature. There is no filler or redundant prose.

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 zero-parameter, read-only list endpoint with robust annotations, the description contains the essential invocation facts: method, path, category, and required scope. It does not describe the response shape, but no output schema is provided and 'List export' reasonably implies a list of export results.

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 has zero parameters and 100% coverage, so there is no parameter gap for the description to fill. The 0-parameter baseline applies; no parameter explanation is necessary.

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?

'List export' names a clear verb and resource, and the HTTP path `/v1/migration/sites/export` plus category 'Migrations' identify it as the migration site export list endpoint. It is distinct enough from the migration list/id siblings, though it could more explicitly say it returns migration site 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 guidance on when to use this endpoint versus sibling migration tools, and no alternatives or exclusions are mentioned. The scope and read-only notes are prerequisites, not selection guidance.

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