get_tutorial_details

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

With no annotations, the description carries full burden. It discloses that the tool returns full content, lists return fields, and specifies that slug comes from search. It implies read-only behavior and does not mention side effects. Adequate transparency.

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?

Extremely concise: front-loaded summary, then param docs, then return fields, then usage. Every sentence adds value. No redundant or filler text.

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?

Covers all necessary aspects: what it does, parameters, return values, and usage context. Given the simple nature and absence of output schema, the description is fully complete for agent decision-making.

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 0%, so description compensates. Explains slug as 'Tutorial slug (from search_mcp_tutorials)' and lang as 'en | ru. Default: en.' Adds meaning beyond schema types and defaults. Could mention that lang controls language of content, but still clear.

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?

Clearly states it retrieves full tutorial content (markdown) with steps, code, screenshots. Explicitly distinguishes from search_mcp_tutorials by saying 'Use this AFTER finding a relevant tutorial via search.' Purpose is specific and 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?

Provides explicit usage instruction: 'Use this AFTER finding a relevant tutorial via search.' Also explains how to use the content (render directly or extract commands/config). No explicit when-not-to-use, but the context makes it clear.

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