append_context

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 usefully discloses that it separates appended content with a blank line, and that it will create the subtopic if missing. However, it doesn't disclose what happens to existing content on append failure, whether the operation is idempotent, or what the return/response format is since there is an output schema.

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 appropriately short — two sentences, minimal waste. The key operational detail (blank line separation) is included in the second sentence. It could arguably be a 5, but the brevity leaves room for adding more meaningful content, so the conciseness is good but the efficiency comes at the cost of missing parameter clarity.

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?

There is an output schema present, so return value explanation isn't required. However, with 0% schema coverage on 2 parameters, no annotations, and no guidance on ref syntax or content format, the documentation is incomplete. The blank-line behavior is disclosed but many operational details (failure modes, idempotency, ordering guarantees) are absent. For a tool with two required params and an output schema, this is a minimum viable description.

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%, meaning neither 'ref' nor 'content' has schema-level descriptions. The description does not explain what 'ref' refers to (a subtopic reference evidently) or what format 'content' should take. 'Creating it if missing' implies ref points to a subtopic, but no syntax, format, or constraints are given for either parameter. The description fails to compensate for the zero coverage.

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 is clear: 'Append content to a subtopic, creating it if missing' is a specific verb+resource with a clear operation. It distinguishes from upsert_context (an upsert overwrites/replaces) by specifying 'append' (add to existing) and 'creating if missing.' However, it doesn't explicitly contrast with siblings like get_context or import_content.

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 states what it does but not explicitly when to use it vs alternatives. The distinction from upsert_context (append vs upsert) is implied through the verb 'append.' There's no explicit 'use this when' language or mention of alternatives, though the append-vs-create semantics provide some guidance on when this is appropriate.

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