Read backlog memory

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds specific operational context by naming the exact file path and its structure (TODO/DOING/DONE), which is useful beyond what annotations state. It does not cover edge cases like missing files or encoding.

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?

A single sentence that is direct and free of filler. It clearly states what the tool does and the target resource without unnecessary words.

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 read operation with good annotations, the description provides essential context (file path and content sections). It does not explicitly state the return format or maxBytes significance, but these are minor gaps given the tool's simplicity and the sibling tool set.

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 schema explains projectPath as an absolute directory path. The description adds meaning by indicating that the file path is relative to projectPath, but maxBytes is left without any description, and the overall schema coverage is only 50%. The description does not fully compensate for the undocumented parameter.

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 the specific verb 'Read' with an exact resource 'docs/memory/backlog.md', and clarifies the file contains TODO, DOING, and DONE items. This makes it distinct from sibling memory tools like read_onboarding_memory or read_project_memory.

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?

It is implied that this tool is for reading the backlog memory file, but there is no explicit guidance on when to use it over alternative memory readers. The sibling list includes many similar read_memory_* tools, yet the description does not distinguish usage cases.

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