coda_append_page_content

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

With no annotations provided, the description carries full burden for behavioral disclosure. It correctly states that content is appended to the end of a page, which is a minimal but accurate behavioral trait. However, it omits details like idempotency, required permissions, or behavior on duplicate content. The description is not misleading but lacks depth.

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 a single, front-loaded sentence with no filler words. Every word adds meaning: 'Append' (action), 'new markdown content' (what), 'to the end of a page' (where). It is appropriately sized for a simple tool with three straightforward parameters.

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 that the tool has no output schema, the description should explain what the caller can expect as a result (e.g., success indicator, updated page content). It also lacks context for selection among siblings: for instance, it does not mention that this tool is for adding content without altering existing content, unlike 'replace_page_content'. Error conditions (e.g., page not found, content size limits) are unaddressed. The description is incomplete for a practical agent.

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?

The input schema has 100% description coverage: each parameter has a clear description. The tool description does not add any additional meaning beyond the schema. For example, it does not provide examples, formatting tips, or explain how 'pageIdOrName' should be formatted. Thus, it meets the baseline but does not exceed it.

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 specifies the action ('append'), the resource ('page'), and the content format ('markdown'). It effectively distinguishes from sibling tools like 'replace_page_content' which overwrites, and 'get_page_content' which reads, making the purpose 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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not differentiate from 'coda_replace_page_content' or mention scenarios where appending is preferred over replacing or inserting. This lack of direction forces the agent to rely solely on tool names and schema.

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