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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's value-add is enumerating the aggregated payload (customer, address/route, assignments, trips, time entries, documents), which hints at a heavy composite read, but it says nothing about response size, pagination, or access requirements, and with no output schema the enumeration is only partial.

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: the operation and its key parameter come first, followed by the payload contents. No filler, no restatement of the title.

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?

For a one-parameter, read-only tool whose annotations cover safety, the description supplies the one thing structured fields don't: what the returned detail bundle contains. Only gaps are the absence of any output schema and any note on payload size or depth, which is minor at this complexity.

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?

With a single parameter and 100% schema description coverage, the schema already carries the meaning ('Project id, as returned by the project list'). The description reinforces that the parameter identifies exactly one project, adding a small amount of clarity on scoping beyond the schema, though nothing on format or validation.

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?

Specific verb+resource: 'Full details of one project by projectId', followed by an enumeration of what those details include (customer, address and route, assignments, trips, time entries, documents). This clearly separates it from list-style siblings like fetchProjectsContext by emphasizing a single project. It stops short of naming a specific alternative such as fetchProjectBoard, so it is not a full 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?

Usage is only implied: an agent infers it should call this when it has a projectId and needs the complete project record. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling for partial views (e.g. board or time-tracking views of the same project). Minimum viable guidance.

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