Save to Section

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

No annotations are provided, so the description carries the behavioral burden. It does disclose one useful side effect: 'Creates it if needed.' However, it does not clarify whether content is appended, overwritten, or how existing content in the section is affected, leaving meaningful ambiguity for a write operation.

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 short sentences with no filler. The core action is front-loaded, and the auto-create behavior is stated immediately after, making it easy to scan and understand.

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?

For a simple two-parameter tool, the description covers the essential action and an important edge case (auto-creation). However, because there is no output schema and no annotations, the absence of append-versus-replace semantics and return-value behavior leaves the description merely adequate rather than complete.

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 100%, so the parameters are already documented. The description adds only light context by calling the target a 'categorized section' and the content 'info,' but it does not enrich parameter semantics beyond the schema. This matches the baseline of 3.

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 uses a specific verb plus resource: 'Add info to a categorized section' and adds the auto-create behavior. It clearly distinguishes itself from a generic save operation, but does not explicitly differentiate itself from siblings like save_memory or update_memory.

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 usage context is implied: use this when adding info to a section, creating it if it doesn't exist. However, the description provides no explicit exclusions or mention of alternatives, so an agent must infer when to choose this over save_memory, update_memory, or replace_section.

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