recent_changes

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

Annotations already declare readOnlyHint and openWorldHint=false, and the description adds real context beyond them: private-folder files are excluded, results are newest-first, and the cap is 50. 'Read only' merely restates the annotation and the return shape is covered by the output schema, so it stops short of 5.

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?

Front-loaded with the core behavior, then exclusions, then alternatives and next step — a sensible order. A few clauses restate structured data ('Read only', 'at most 50'), which keeps it from a perfect score.

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 single optional-parameter read tool with an output schema and annotations, the description covers scope, exclusions, ordering, alternatives, and the natural follow-up call. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100% and the limit parameter is fully documented in the schema (default 15, max 50). The description only echoes 'up to limit, at most 50', adding no new semantics such as what ordering or counting rules apply to the limit. Baseline 3 applies when the schema does the work.

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?

States a specific verb and resource ('List the notes and files changed most recently') plus ordering ('newest first') and scope ('in every unlocked folder'). It explicitly distinguishes itself from search_notes (topic lookup) and list_notes (folder browsing), so an agent can route without opening schemas.

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?

Gives concrete when-to-use triggers ('what did I work on lately', 'pick up where the person left off') and names the two alternatives with the conditions that select them. It also gives the follow-up action (read_file_text by path), leaving nothing to inference.

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