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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that content is authored from markdown, but says nothing about whether each call creates a distinct new block, position defaults, or editing implications for an existing block.

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 sentence, front-loaded with the core action and resource. The trailing list of example content types is a bit list-heavy but does useful disambiguation work, so it largely earns its place.

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 five parameters, 80% schema coverage, annotations present, and no output schema, the description covers the core purpose but omits what the tool returns (e.g., a block id needed for later edit_block/read_block calls) and gives no guidance on placement. Adequate but with visible gaps for a mutating tool.

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 80%, with clear docs for boardId, title, markdown, and x (the y parameter is left undocumented). The description only reinforces that the content parameter is markdown, adding little beyond what the schema already states, so the baseline 3 applies.

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 concrete action and resource: writing markdown content onto a Flett board as a 'document block', with a concrete list of content types. It distinguishes itself reasonably from add_file/add_map, though it never explicitly contrasts with the closest sibling add_block, which also creates content on a board.

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 enumerated content types (notes, explanation, report, comparison, study guide, plan) imply when this tool is appropriate, but there is no explicit routing guidance against add_block, add_file, or edit_block. The agent must infer the boundary between this and generic block creation.

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