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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds content-nature context (digest is 'as emailed to subscribers', weekly is 'analysis'), but nothing about pagination, archive size, or freshness limits beyond the annotations.

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 sentences, zero waste, and the two editions are defined before the parameter-recipe sentence. Every clause earns its place.

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 retrieval tool with no output schema, the description covers what the editions are and how to reach the latest vs. the archive. Combined with 100% schema coverage and full annotations, an agent has enough to call it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds the combination semantics the schema states only piecewise: omitting date and slug yields the latest edition, and list=true switches to the archive. It notably omits any mention of the 'kind' and 'detail' parameters, which the schema carries alone.

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 names the resource precisely — Mappit's two editorial editions, the Daily Digest and the Week in Review — and characterizes each (top stories worldwide vs. weekly analysis). An agent can tell this apart from siblings like get_story or list_stories, though it never states an explicit verb and does not name a sibling it is not.

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 gives clear conditional guidance: omit date and slug for the latest edition, set list to true for the archive. That covers the main usage forks for a zero-required-parameter tool. It stops short of naming alternative tools or stating when *not* to use this one.

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