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

No annotations are provided, so the description carries the full burden. It discloses that the result is deliberately "compact" versus the full state, which is useful behavioral context, but it says nothing about read-only safety, permissions, page/size limits, or whether truncation can occur.

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 front-loaded sentence that leads with the verb and payload before the sibling comparison. The stray section marker "(§16)" is dead weight referencing context the agent cannot see.

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?

With no output schema, the enumeration of returned contents partially covers the return shape, which is valuable for a summary tool. However, the sole input parameter is completely undocumented in both schema and description, leaving a gap for such a simple tool.

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 single parameter projectId has 0% schema description coverage and the description never mentions it — no format hints, no source of the ID, no required/optional framing. With one undocumented parameter, the description should have compensated and does not.

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?

Uses a specific verb ("Fetch") and resource ("compact project summary") and enumerates the payload (project settings, tracks, scene list), which tells an agent exactly what comes back. It also names the sibling it supersedes. The unexplained "(§16)" reference adds noise rather than clarity, which keeps it short of a 5.

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?

Explicitly routes the agent away from project.get_state for "normal conversation context," which is a real alternative-plus-condition pairing. It does not state when get_state would actually be preferred (e.g., full detailed state, mutations, undo), so the exclusion boundary is only half-drawn.

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