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

readOnlyHint=true already establishes the safety profile, so the description adds value by disclosing what data comes back (balances, giving history, gift/giver counts) – especially useful since there is no output schema. It omits details like permissions or pagination, but this is a low-risk read.

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 compact sentences, front-loaded with the verb+resource and followed by the field list and API path. The dense field enumeration earns its place given the missing output schema, though it is slightly list-heavy.

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 tool with annotations covering safety, the description is essentially complete: it names the resource, the input, and enumerates return fields to compensate for the absent output schema. Only the relationship to the project-search sibling is left implicit.

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 project_id parameter is fully documented in the schema, so the baseline of 3 applies. "GET /api/Project/{projectId}" restates the parameter rather than adding format or constraint detail.

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 opens with a specific verb+resource ("Fetch one project") and enumerates the returned fields, making the tool's scope unambiguous. It contrasts implicitly with the sibling virtuous_search_projects via "one project," though it never names that sibling.

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 implied by "Fetch one project" and the projectId in the endpoint template, so an agent can infer this is the single-record lookup to use when it already has an id. There is no explicit when-to-use vs. when-not, and no mention of the search alternative.

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