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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the response is markdown and terminates in the project's canonical URL. It stops short of noting response size, latency, or behavior for an unknown slug.

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?

Single sentence, front-loaded with the resource identity and no filler. However it is a verbless noun phrase with a long colon-delimited field list, which is dense to scan and slightly harder to parse than a short declarative.

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 the description need not explain return values, and parameters are fully specified in-schema. The description supplies the markdown format and canonical-URL ending, which is enough for correct invocation of a simple two-parameter read 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?

Schema coverage is 100% and both parameters are documented in-schema (slug as the last path segment of /projects/, lang enumerated with a default), so the schema carries the load. The description adds nothing about parameters, so 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?

The description names the resource precisely ('One tracked project') and enumerates the payload contents (parties, value, financing, status against schedule, variations, documents, coverage), which distinguishes it from a search/list tool. What it lacks is an explicit verb and any naming of siblings such as list_projects or get_entity_record, so differentiation is inferred rather than stated.

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?

Usage is only implied: the word 'One' signals a single-project retrieval versus the list_projects sibling. There is no explicit statement of when to prefer this over search_entities or get_document, and no prerequisite or exclusion guidance.

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