Project Status

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

No annotations are provided, so the description carries the full behavioral burden and falls short. It implies a read ("Return") but never states that explicitly, nor does it describe what gets returned, whether a missing/unregistered project_id errors or returns empty, or any auth or network requirement.

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 short sentence with no filler, and the purpose is front-loaded. However, brevity here is under-specification rather than economy: the sentence is too thin to be useful for a lookup tool.

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 annotations, no output schema, no param documentation, and an undefined "mapping," an agent has no way to know what it will receive or what state it will change. For a one-parameter lookup whose return value is the entire point, the description is materially incomplete.

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 for the single project_id parameter and does not — no format, no source (local versus remote registration), no statement that it must reference an already-registered project. One trivially-named parameter keeps this above a 1, but the description adds no meaning beyond the key name.

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?

It has a verb and a resource ("Return the registered project mapping"), but "mapping" is undefined jargon and the description never distinguishes this from siblings like project_ensure, project_sync, or project_list_remote_changes. An agent cannot tell from the text alone whether this resolves local-to-remote project identity or merely echoes a stored record.

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, when-not-to-use, or alternative routing in the description. With seven project_* siblings, some criterion for choosing project_status over project_ensure or project_list_remote_changes is essential and entirely absent.

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