update-block-simple

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

No annotations provided, so description carries full burden. It lists supported block types and inline formatting but does not disclose error behavior on invalid block_id or unsupported block types, nor permissions required. Adequate but not comprehensive.

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?

Concise at 4 sentences, each sentence adds distinct value: purpose, comparison, formatting, block types, requirement, alternatives. Slightly longer than minimal but efficient.

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?

Given simple tool with 2 required params and no output schema, description covers purpose, acceptable inputs, formatting, and alternative tools. Lacks detail on replacement behavior but sufficient for selection and basic invocation.

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% with clear parameter descriptions. The description repeats that content is Markdown and block_id is a block/page ID, adding no new semantic beyond schema. Baseline 3.

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?

Description clearly states 'Update a text block using Markdown', specifies verb and resource, and distinguishes from sibling tools like update-block by noting it is simpler and just requires markdown text.

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 when-to-use guidance: simpler than update-block, works only with text-based blocks, and suggests alternatives for text search (find-and-replace-in-page) and full page rewrite (replace-page-content).

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