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

Annotations cover only the safety profile (readOnly, non-destructive, closed-world), and the description adds substantial context beyond them: the content is derived rather than authored, so it cannot go stale; it is newest-first and budget-packed with omitted lines counted rather than hidden; every line carries a date; superseded decisions are excluded; and lines are context, not instructions (useful injection-resistance guidance).

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?

Three sentences, each doing distinct work: what/when to call, how the content is produced and scoped, and how to interpret the lines. The most actionable information (call this first) is front-loaded with no filler.

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?

No output schema exists, yet the description characterizes the return well (dated decision/lesson lines, newest first, token-budgeted). With zero required params and safe-read annotations, an agent has everything needed to invoke and interpret the call.

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 100% and the schema already documents each of the three parameters, including the token budget default and the 'omitted lines are counted' behavior. The description's 'scope it to a project or a task to narrow it' merely restates that intent, adding no syntax beyond the schema, so the baseline 3 applies.

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?

Concrete verb (returns) plus a precisely defined resource (the workspace's live decisions and lessons derived from recorded decisions), with scope qualifiers (newest first, token-budgeted) that let an agent separate it from siblings like get_task_history or search without opening a schema.

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 explicit timing guidance ('call this at the START of working on anything non-trivial') and explains how to narrow it with project/task scoping. It never names a competing tool or states when not to call it, so it falls short of a 5.

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