list_recent

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

With no annotations, the description must fully disclose behavior. It mentions the tool lists recent notes and returns specific fields, but does not explain the effect of the limit parameter, ordering (ascending/descending), or any side effects. The behavioral profile is incomplete.

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 a single sentence of 10 words, front-loading the main purpose efficiently. No redundant information is present.

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 tool with one parameter and an output schema, the description is too sparse. It omits crucial context: the limit parameter's role, the exact ordering (e.g., descending by update time), scope (user-specific?), and implications of default limit. Output schema exists but does not justify these omissions.

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% and the tool description does not mention the single parameter 'limit' at all. It fails to add meaning beyond the schema, leaving the agent to guess that limit controls result count.

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 action ('List'), the resource ('most recently updated notes'), and the returned fields (id, title, updated time). It effectively distinguishes from sibling list tools like list_notes_by_tag and list_notes_in_notebook by specifying recency ordering.

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 provides no guidance on when or when not to use this tool versus alternatives. There is no mention of context, prerequisites, or implicit usage conditions. Missing any comparative or contraindicative information.

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