insert_after_heading_fs_tool

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

No annotations provided, so description carries full burden. Discloses case-sensitive matching, first-occurrence insertion, and a performance note (10k words <500ms). Lacks details on error handling (e.g., heading not found) or side effects, but covers core behavior adequately.

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?

Well-structured with sections for purpose, details, when to use, performance, and returns. Front-loaded with purpose, each sentence adds value, no fluff. Efficient and clear.

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 simplicity of tool, high schema coverage, and no output schema, description covers all necessary aspects: behavior (case-sensitivity, first occurrence), usage scenarios, performance, and return value. Complete for task of inserting after a heading.

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 80% (ctx parameter lacks description). Description adds examples for filepath and heading, clarifies heading should be without #, and explains content parameter. Does not elaborate on 'ctx' parameter, but overall adds marginal value over 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?

Description clearly states 'Insert content immediately after a specific heading in a note,' with specific verb (insert), resource (content after heading), and behavior (case-sensitive, first occurrence). Distinguishes from sibling insert_after_block_fs_tool which inserts after a block rather than a heading.

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?

Provides explicit 'When to use' list (e.g., adding tasks to Tasks section, inserting notes under Notes heading) giving clear context for appropriate use. Does not explicitly contrast with alternatives or state when not to use, but the listed scenarios are specific enough.

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