list_sections

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

With no annotations provided, the description carries the burden of behavioral disclosure. It appropriately implies a read-only listing operation ('List all sections') and notes a dependency on notebook_id, but it does not describe return format, ordering, or possible errors. For a simple list tool, this is minimally adequate.

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 sentences, each earning its place. The first states the action precisely, and the second provides a necessary usage guideline. There is no redundancy or unnecessary detail.

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 the tool's simplicity (one param, no output schema, no annotations), the description adequately covers its purpose and the required usage sequence. It lacks return format details, but the tool name and the obvious outcome ('list all sections') make it reasonably complete for an agent to invoke correctly.

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?

The schema already provides 100% coverage with a basic parameter description ('The ID of the OneNote notebook'). The tool description adds meaningful context by stating 'Use list_notebooks first to get the notebook ID,' clarifying the source of the parameter and the prerequisite step, which goes beyond the schema's type-only description.

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 'List all sections in a specific OneNote notebook' with a specific verb and resource. It distinguishes from sibling list_notebooks by specifying the notebook scope and directing the user to first call list_notebooks.

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 context: 'Use list_notebooks first to get the notebook ID.' This clearly indicates when this tool should be used (after obtaining a notebook ID). It does not mention alternatives or when not to use it, but the prerequisite guidance is valuable.

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