edit_context_item

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

No annotations are provided, so the description must disclose behavioral traits on its own. It only states it edits content and/or tags, but fails to mention any side effects, permission requirements, or the behavior of partial updates (e.g., whether providing only tags will leave content unchanged). No such context is added beyond the basic purpose.

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. It is appropriately concise, though extremely brief. It earns a high score for structure and efficiency, but not a 5 because it omits contextual details that could be helpful without much added length.

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 tool has five parameters, is a mutation operation, and has no output schema, the description is incomplete. It does not mention return behavior, whether the removal of tags is allowed, or how the 'sync' parameter affects the operation. The schema partially compensates, but the description fails to provide a holistic understanding of the tool's behavior.

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, so the baseline is 3. The description does not add meaning beyond the schema—it only mentions 'content and/or tags', which are already defined. It provides no extra insight into the 'path' or 'sync' parameters beyond their schema descriptions.

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 states the tool edits an existing context item's content and/or tags using its ID. This uses a specific verb ('edit') and resource ('context item'), and distinguishes it from sibling tools like add_context_item or list_context_items.

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?

There is no explicit guidance on when to use this tool compared to alternatives. The description only implies usage via the verb 'edit', but does not mention prerequisites, exclusions, or when to prefer sibling tools like add_context_item or remove_context_item.

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