read_section

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

No annotations are provided, so the description carries the full burden. It states the tool reads content, implying non-destructive behavior, but does not disclose any side effects, permissions, rate limits, or data format specifics (e.g., markdown, plain text). The output schema exists but the description does not hint at return structure.

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 short (two lines for args, one line for purpose) and front-loaded. However, it includes 'Args:' which is redundant if the schema is present. Still, it is concise and well-structured for quick understanding.

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 tool with an output schema, the description is minimally complete: it explains inputs and basic function. It lacks pre/error conditions or comparative context with siblings. Given the low complexity and existence of output schema, the description is adequate but could be more informative.

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 input schema has no parameter descriptions, so the description adds significant value by explaining that 'section_name' should come from 'list_sections' and 'notebook_name' is the notebook name. This is helpful and compensates for the 0% schema description coverage.

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 verb 'Read' and the resource 'all text content from a specific section of a notebook'. This distinguishes it from sibling tools like list_sections (list only) and search_notes (search across sections). The specificity is high.

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 indicates the tool reads a section's text content, but provides no guidance on when to use it versus alternatives (e.g., list_sections for listing, search_notes for querying). It relies on the user to infer usage context from the tool name and description.

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