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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered structurally. The description adds value by disclosing the three return formats, enriching the agent's expectation of the response, though it does not go into detail about what each artifact mode contains. This is adequate but not rich behavioral context 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 with zero filler. The primary action is front-loaded, and the usage tip is appended as the second sentence. Every word earns its place; no redundant phrasing or restatement of the title.

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 fetch tool with an output schema, this is largely complete: it names the resource, scope, artifact modes, and a recommended default. It does not elaborate on the semantic difference between the three artifact types or document the slug format, but these are minor gaps given the self-explanatory mode names and the presence of an output schema covering return values.

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 the description must compensate. It does explain the 'artifact' parameter's enum by naming its three modes (metadata, machine brief, dossier), adding meaning beyond the bare enum values. However, the required 'slug' parameter has no semantic or example context in either the schema (which only shows a regex pattern) or the description, leaving a gap for the one required parameter.

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?

States a specific verb (Fetch) and resource (one story), and precisely defines the three artifact modes it returns: metadata, machine brief, or cited dossier. These artifact types clearly separate it from sibling tools like get_newsroom (fetches an entire newsroom), get_overview, and the get_palimpsest_* family, so an agent can distinguish it without opening schemas.

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?

Offers one genuine usage tip — 'Use the machine brief first for agent workflows' — which guides the default artifact choice. However, it gives no when-not-to-use guidance and does not reference alternative tools (e.g., when to call get_newsroom or get_overview instead). The guidance is artifact-level rather than tool-selection-level.

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