project_context

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

With no annotations, the description carries the full burden. 'Read' and 'compact' do convey that this is a non-mutating, summarized call, which is useful signal. It does not confirm read-only status explicitly, state freshness or scope limits of the snapshot, or note that a compact view may omit detail.

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 with no filler; the verb and resource lead and the content list is packed into the same clause. Nothing could be removed without losing information.

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?

There is no output schema, so the description's enumeration of the returned domains effectively serves as the return-value description, which is reasonable for a zero-parameter read tool. The only real gap is the absence of any behavioral or scoping note, which matters more given there are no annotations.

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 tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and the enumerated contents help the agent understand what the call returns without parameters.

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 ('Read') and resource ('project snapshot') and enumerates what the snapshot contains (agents, tasks, messages, artifacts, decisions), so the agent knows exactly what it gets. It does not, however, differentiate itself from siblings like task_manage or agent_message, e.g. by stating that this is the aggregate read versus their per-domain operations.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. The agent can infer it is an orientation call made before acting, but the description never says so, nor does it distinguish this from the domain-specific siblings.

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