List sections

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

The readOnlyHint annotation already covers safety, so the description isn't burdened with that. It adds meaningful behavioral context by explaining that nested sections are included and that the result is a flat list rather than a hierarchical outline. It doesn't describe pagination details, but the schema already covers that via the limit parameter.

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?

Two sentences, no fluff, with the most critical information front-loaded. It states the core function first and then provides an actionable preference. Every word earns its place.

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 read-only list tool with two optional parameters and no output schema, the description is complete. It explains the tool's scope, the nested behavior, and how to choose between this and the sibling getOutline. The readOnlyHint annotation covers safety, so no further behavioral disclosure is needed.

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 fully documented in the schema. The description doesn't add any parameter-specific meaning beyond what's in the schema. The baseline of 3 is appropriate since the description provides no extra parametric insight yet doesn't need to.

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's function: 'List sections, including those nested inside section groups.' The verb 'List' and resource 'sections' are specific, and the nested-group detail adds precise scope. It also distinguishes from the sibling 'getOutline' by explicitly contrasting a flat list with an outline.

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 gives explicit usage guidance: 'Prefer getOutline unless you specifically want a flat list.' This tells the agent when to use this tool versus the main alternative, which is exactly what a usage guideline should do.

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