read_node_as_markdown

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it warns about potential large outputs, explains how to limit output size with max_depth, and provides important usage guidance for bypass_warning. It doesn't mention rate limits, authentication needs, or error conditions, but covers the most critical operational aspects.

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 description is perfectly front-loaded with the core purpose, followed by parameter guidance and a critical warning. Every sentence earns its place: the first states what the tool does, the second explains input options, and the third provides essential operational guidance. No wasted words.

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 operation with no annotations and no output schema, the description provides good coverage of the tool's behavior and limitations. It addresses the most critical concern (output size management) and gives practical parameter guidance. The main gap is lack of information about the return format structure beyond 'Markdown' - but given this is a conversion tool, that may be sufficient.

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 already documents all 7 parameters thoroughly. The description adds minimal value beyond the schema - it mentions the URL format with optional deep link and reiterates the max_depth purpose, but doesn't provide additional semantic context about parameter interactions or edge cases.

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 clearly states the specific action ('Read a Dynalist document or specific node') and output format ('return it as Markdown'), distinguishing it from siblings like edit_node or delete_node which perform modifications. It explicitly mentions the resource type (Dynalist document/node) and transformation (to Markdown).

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 provides clear context for when to use this tool (reading documents/nodes as Markdown) and includes a practical warning about large documents. However, it doesn't explicitly mention when NOT to use it or name specific alternatives among the sibling tools (e.g., search_in_document for finding content without full conversion).

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