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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description adds the useful detail that results come back in tab order, plus the field set of each entry, but says nothing about pagination, limits, or what happens for a campaign with no maps.

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 first sentence is dense and front-loaded with the useful field list, but the trailing 'Returns: The maps.' is a near-tautology that restates the tool name and earns no place. Net length is fine, structure slightly awkward.

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 single-parameter read with full annotation coverage, the description is largely sufficient, and since there is no output schema, listing the returned fields (id, name, size in pixels, pin count) is genuinely valuable. Ordering information is a bonus; only edge-case behavior 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% for the single campaign parameter, and the schema already explains slug-or-id acceptance. The description adds no further meaning about the parameter, so the baseline 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 description conveys that it retrieves a campaign's maps in tab order, but there is no explicit verb (list/fetch) — the action is only implied by the possessive noun phrase and the name. It does name the concrete resource (maps) and the returned fields, which distinguishes it somewhat from siblings like list_pins, but it never states the relationship to those pin tools.

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 when-to-use guidance and no mention of alternatives such as list_pins, list_my_private_pins, or update_map. An agent must infer from the name alone that this is the read path for map metadata within a campaign.

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