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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds behavior beyond them: which related entities are hydrated in the response and an explicit rule that UUIDs must never be surfaced to the user, which is real operational guidance an agent would otherwise get wrong.

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?

Two sentences, both earning their place, with the core verb and resource front-loaded. The second sentence is a non-obvious output rule rather than filler, though it is long enough that the lookup purpose briefly gets buried.

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 values need not be explained further, and the description still usefully names the included sub-resources. The only gap is the absence of any routing signal versus the sibling list/set tools for what is otherwise a simple one-parameter reader.

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 100% and the single parameter already documents 'Project id (UUID) or slug'. The description repeats the id-or-slug acceptance without adding format or resolution details, so the baseline 3 applies.

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+resource ('Get a single project by its id or slug') and adds what the response contains (languages, connected repository). It does not differentiate itself from the sibling list_projects or set_project_context, so an agent must infer the singular-vs-list distinction from the name alone.

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?

The description implies a lookup flow (you must already have an id or slug) but never states when to use this tool instead of list_projects, nor any prerequisite for obtaining the identifier. It does add a reply-formatting rule, but that is output presentation guidance, not usage guidance.

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