memory_create_section

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

With no annotations, the description fully discloses key traits: sections are not graph-visible, excluded from duplicate detection, and lack embeddings or cross-references. Also mentions auto-assigned tag.

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 well-structured with a clear first sentence, bullet-pointed behavioral notes, and an Args section. Each sentence is informative and earned.

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?

Covers purpose, behavioral traits, parameter semantics, and return value (with auto-assigned tag). Given the output schema exists, the return description is sufficient.

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?

Despite 0% schema description coverage, the 'Args' section explains each parameter with examples (e.g., section: 'Architecture', subsection: 'endpoints/auth'), adding significant meaning beyond the schema.

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 states 'Create a new section/subsection header memory' with specific verb and resource. It distinguishes from sibling tools like memory_create by detailing unique behaviors: not visible in graph, no duplicate detection, no embeddings.

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 clearly implies usage for organizational placeholders but does not explicitly contrast with siblings like memory_create or memory_create_issue. The context from behavioral traits helps, but explicit when-to-use guidance is missing.

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