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

With no annotations the description must carry the full burden, and it does disclose meaningful traits: the operation is cheap, it is a read by default, and set_status explicitly overwrites (destroys) the existing status line, with an example of the format. It omits permissions/auth requirements and whether other project state is affected.

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 short sentences, front-loaded with the read purpose, followed by the write mode and the usage rationale; the inline example earns its space by fixing the expected value format. 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?

An output schema exists, so return contents need not be explained (the description describes them anyway). The dual read/write nature, cost and intended use are covered; only the 'project' parameter's semantics and any permission/error behavior remain unaddressed.

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 compensate. It explains set_status well, including a concrete example value, but says nothing about the required 'project' parameter beyond what its name implies, leaving half the parameters undocumented in both schema and prose.

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 ('Get') and resource ('the project's one-line status, open tasks and last change'), and even enumerates the returned fields, plus the secondary write mode via set_status. It does not explicitly distinguish itself from siblings like project_open, recall, remember or update, which keeps it out of the top band.

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?

"Cheap; use it for handoff notes between sessions" gives clear usage context and the set_status example implies when to write versus read. There are no explicit when-not conditions and no named alternatives among the overlapping siblings (recall/remember), so it stops short of 5.

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