list_all_sections

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

No annotations present, so description bears full weight. It states the action but doesn't discuss potential pagination, performance, or whether it retrieves all data at once. Adequate for a simple read tool.

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 focused sentences, no fluff. Perfectly concise for the simple tool.

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 simplicity (no params, output schema present), the description covers the essential context. Could mention potential large payloads, but overall complete enough.

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?

No parameters, so schema coverage is trivial. Description adds value by clarifying the scope ('ALL notebooks'), ensuring the agent knows it's a global operation.

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?

Clearly states 'List ALL sections across ALL notebooks' with a specific verb and resource. Distinguishes from sibling 'list_sections' by emphasizing the global scope.

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 a use case ('useful for getting a complete overview') but does not explicitly mention when to avoid or compare with similar tools like list_sections.

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