read_notes

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

With no annotations provided, the description carries the burden of disclosing behavior. It clarifies the return type, line-break separation, and the default message when no notes exist. The read-only nature is implicitly disclosed by the verb 'Read', and no side effects are mentioned, which is adequate for a simple read tool. However, it does not address error conditions (e.g., missing file) or whether any implicit file creation occurs.

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 remarkably concise and well-structured. It opens with the primary purpose, then provides a clearly separated 'Returns' section that explains the output format and a fallback case. Every sentence adds value, and there is no redundant or extraneous text.

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 (no parameters), the description is complete: it states what the tool does, what it returns, and how it handles an empty notes file. The existence of an output schema further reduces the need to explain return values in depth, but the description still provides useful details. The sibling tool names frame its niche as a read operation.

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 tool has zero parameters, so the schema provides no meaningful descriptions. The baseline for zero parameters is 4, and the description does not need to explain any because there are none. The return behavior is described, which partially compensates for the lack of parameters.

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 uses a specific verb ('Read and return') and identifies the resource ('all notes from the sticky note file'). It clearly distinguishes from sibling tools like add_note, delete_notes, and save_to_new_file by indicating a read-only operation with no modifications.

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 implies its usage context (when you need to view all notes) but does not explicitly state when to use it over alternatives or mention any exclusions. It provides no direct comparison to sibling tools, leaving usage somewhat inferred rather than explicit.

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