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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is well covered by structured data. The description adds real value by disclosing that results include steps, caveats, and primary sources, but it says nothing about pagination behavior despite limit/cursor parameters existing. Adequate but not rich.

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?

Two tight sentences with the content scope first and the filtering mechanism second; nothing is wasted. Slightly penalized only because the front-loaded scope contains the import/export ambiguity.

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?

An output schema exists, so return value explanation is unnecessary and correctly omitted. However, for a 4-parameter paginated list tool, the description never accounts for limit/cursor and carries the naming inconsistency, so it is not fully complete.

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%, so all four parameters rest on the description. It mentions 'exact slug' (usefully signaling exact-match semantics) and 'category', covering only two of the four parameters. The pagination pair, limit and cursor, is completely undocumented in both the schema and the description, leaving a real gap.

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 read verb and enumerates the resource contents (formats, steps, caveats, sources), but it calls these 'synthesizer import formats' while the tool name is 'list_export_targets'. That import/export mismatch creates ambiguity about what is actually being listed. The resource is broadly identifiable, but the internal inconsistency keeps it from being a clean 4-5.

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?

The description implies usage through 'Filter by exact slug or category', telling the agent how to narrow results. However, it names no alternative tool and gives no explicit when-to-use or when-not-to-use condition relative to the sibling tools. Usage is inferable but not directed.

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