postit.read_section

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

With no annotations, the description carries the full burden of safety and behavior. It usefully discloses the matching rule (case-insensitive, exact), but does not explain what happens if no heading matches, if multiple match, or whether subheadings are included. Still, it adds meaningful behavioral context beyond what the schema provides.

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. Every word adds value by specifying the action, resource, and matching exactness.

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 a nested requirement (name and heading are required), an output schema, and no annotations, yet the description is minimal. It omits critical parameter meanings (name, level, dir) and does not explain the return format or edge cases. Sibling tools exist but no comparison is provided, making it incomplete for correct invocation.

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 0%, so the description must compensate by explaining parameters. It only clarifies the 'heading' matching semantics. The required 'name' parameter and optional 'level' and 'dir' parameters are not mentioned, leaving the agent to guess how to specify which document and heading level to target.

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 the specific verb 'Read' and identifies the resource as 'markdown section', with clear matching criteria (heading text, case-insensitive, exact). This distinguishes it from sibling read tools like postit.read or postit.read_lines, which presumably read the whole note or lines.

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 implies when to use this tool (read a specific section by heading) but provides no explicit guidance on when not to use it or how it compares to alternatives like postit.read, postit.read_lines, or postit.search. It lacks exclusions or named alternatives.

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