get_essay

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

With no annotations, the description carries the burden of disclosing behavior. 'Retrieve' signals a read-only operation and the sentence states the main output formats. It does not cover error handling, missing slugs, or auth requirements, but for a simple fetch tool the core behavior is transparent.

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?

A single, front-loaded sentence conveys purpose and output options with no filler. Every word earns its place and key information appears immediately.

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 two-parameter retrieval tool, the description plus schema covers the essential call pattern and return formats. It lacks explicit exclusions and error behavior, but that is a minor gap for this simple operation.

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%, so the schema fully documents slug and format. The description adds no new semantic detail beyond restating that it returns full, summary, or markdown content, matching the schema enum. Baseline 3 is appropriate.

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 a clear verb ('Retrieve'), a specific resource ('a specific essay'), and the key identifier ('slug'). This clearly differentiates it from siblings like list_essays and search_essays, which operate at collection level.

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 phrase 'by its slug' implies this is the tool to use when the caller already knows which essay is wanted, as opposed to list_essays or search_essays. However, it never explicitly states when not to use it or names an alternative, so guidance is only implied.

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