append_to_section

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

No annotations are provided, so the description carries the full burden. It discloses the precedence of input_file over content and supports content_format choices ('markdown' or 'storage'), which is useful. However, it omits side effects (e.g., whether a new version is created), permission requirements, or error conditions—important for a mutation tool.

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 front-loaded with a one-sentence summary, followed by a clean, bulleted Args list. Every sentence serves a purpose, with no redundant or extraneous information. It is both concise and well-structured.

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 the presence of an output schema and moderate complexity (6 params), the description is largely complete: it covers all parameters and the core behavior. It lacks behavioral context like versioning impact or permission prerequisites, but these are not required by the schema. Overall, it adequately informs an agent about what the tool does and how to invoke it.

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 0%, but the description compensates by listing all six parameters with meaningful explanations. It adds semantics beyond the schema by stating 'content ignored if input_file is provided' and clarifying the content_format options and optional nature of version_message.

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 explicitly states 'Append content to the end of a specific section,' which uses a specific verb and resource, and accurately differentiates from sibling tools like update_section (which would replace content). The action is unambiguous and directly aligns with the tool's name.

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 clearly implies usage through the verb 'append' and the target 'specific section,' and the parameter list clarifies when content versus input_file is used. However, it does not explicitly mention when not to use this tool or contrast it with alternatives like update_section or update_page, so it stops short of full when/when-not guidance.

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