List sections

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds domain context (sections are filing categories) but does not disclose extra behavioral details like ordering, pagination, or response shape. This is adequate but not exceptional.

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 with no filler. The main action is stated first, followed by a meaningful purpose statement and a concrete usage pointer. Every sentence 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?

This is a simple, read-only list tool with a single optional parameter and rich annotations. The description explains what the tool returns conceptually and how to use the result, which is sufficient for an agent to call it correctly. No output schema exists, but the mention of section_id fills the key return-value gap.

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 schema fully documents the single 'publication' parameter. The description does not add param-specific details, but none are needed because the schema already explains the loose hostname matching and default behavior.

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 a specific verb and resource: 'List the publication's sections.' It further clarifies what sections are ('categories a post can be filed under') and explains their role, clearly distinguishing this tool from the many post/draft/note management siblings.

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 when-to-use guidance: 'Call this to find the section_id that create_draft and update_draft take.' This tells the agent exactly why it would invoke this tool and which sibling tools depend on its output.

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