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

Annotations already indicate readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful behavioral context by specifying the exact output components (metadata, markdown body, citations) and identifying a canonical valid slug, which goes 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 short sentences with no filler. The first sentence states what the tool does and what it returns, and the second provides a practical usage example. Both sentences earn their 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?

This is a low-complexity, single-parameter tool with a full input schema, an output schema, and annotations covering read-only safety. The description adds a canonical slug example, and sibling tools are available for discovering other slugs. Nothing essential is missing for correct invocation.

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 schema fully documents the slug parameter, so the baseline is 3. The description adds value by connecting a specific slug to its real-world content ('how-to-tell-whos-good' for the lead essay on telling who is good at the job), giving the agent meaningful guidance beyond the schema's example.

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 specific action and resource: 'Returns one Get2Great magazine essay as structured content' with metadata, markdown body, and citations. The word 'one' distinguishes it from the list and search sibling tools, making its role unambiguous.

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 the tool is for retrieving a specific magazine essay by slug, and it provides a concrete example slug for the lead essay. However, it does not explicitly contrast this tool with list_magazine_articles or search_magazine_articles, so an agent must infer when to choose this over alternatives.

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