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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description corroborates with specifics: 'The previous guide is replaced entirely' and non-matching content is 'returned in remainder and kept, not dropped.' It also details the markdown parsing contract (blocks, minutes, key questions, Конспект special case), which is 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?

The purpose and sibling routing are front-loaded, and each sentence carries a distinct parsing rule rather than filler. It is dense and would benefit from list formatting for the markdown grammar, but nothing is redundant.

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?

With no output schema, the description compensates by explaining how non-matching input is surfaced in 'remainder,' and annotations already cover the destructive safety profile. For a format-heavy replace operation, an agent has everything needed to invoke 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 substantially enriches meaning for the markdown parameter: it defines intro text, block headings with minute syntax, question lines, key-question marker, block/question notes, the Конспект exception, and the optional total-time line. This is far more than the schema conveys.

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 opens with a specific verb+resource+scope: 'Replace an existing interview guide from markdown.' It immediately names the sibling it is not (guides_create) and clarifies the replacement semantics, so an agent can distinguish it from guides_create/guides_read without opening any schema.

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 an explicit alternative with its selecting condition: 'To create the first guide, call guides_create.' This routes the agent to the correct sibling for the create case, and 'Replace... entirely' signals the overwrite situation in which this tool is appropriate.

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