stale_notes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does state that results are ordered 'oldest first,' which is a behavioral trait, but it does not explicitly indicate that the operation is read-only, describe the output format (e.g., list of note IDs/titles), or mention any side effects or prerequisites. This is a minimal disclosure.

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 only seven words, which is concise but under-specified. It lacks a complete sentence and omits essential details about the tool's operation and parameters. It is not front-loaded with the most critical information; it simply gives a fragment that could be interpreted in multiple ways.

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 has three parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain any parameter, describe the return value, or provide usage context. An agent would have insufficient information to know how to call the tool correctly or what to expect.

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 0%, so the description must explain the parameters. It does not. The phrase 'N+ days' loosely corresponds to the 'days' parameter, but it never explicitly names or explains 'days', 'limit', or 'folder'. The schema itself is the only source of parameter meaning, and the description adds no clarification.

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 'Notes untouched for N+ days, oldest first' clearly identifies the tool's purpose: it retrieves notes that have not been modified for a specified number of days, sorted by age. The term 'untouched' and the ordering criterion effectively distinguish it from siblings like recent_notes or list_notes, though it lacks an explicit verb such as 'list' or 'retrieve'.

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?

There is no explicit guidance on when to use this tool over alternatives. The name and description imply it is for finding stale notes, but no comparison to recent_notes or other query tools is provided, and there is no mention of appropriate contexts or exclusions.

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