update_algochains_telos

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

The description states the tool is append-only and never overwrites, which contradicts the annotation idempotentHint: true. Since appending multiple times creates distinct entries, the tool is not idempotent, creating a serious inconsistency that could mislead an AI agent.

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 two sentences with no redundant information. The first sentence defines the function, and the second clarifies the use case and behavioral constraint, making it efficient and easy to parse.

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?

The tool has no output schema, and the description does not explain the return value or success confirmation. While the append-only behavior is clear, the lack of output details and the annotation contradiction reduce completeness for this simple mutation tool.

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% coverage with descriptions for all three parameters. The description adds little beyond repeating that the tool appends and listing section types already in the schema. No additional semantics are provided.

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 appends a new entry to an AlgoChains TELOS file, specifying the file types (goals, learned, ideas, etc.) and the append-only behavior. This distinguishes it from the sibling get_algochains_telos and other tools.

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 explicitly says when to use the tool ('capture new lessons learned, ideas, or goal updates during a session') and highlights the append-only constraint. However, it does not mention when not to use it or provide alternatives for overlapping actions like store_trade_lesson.

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