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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it never says what happens for an unknown or malformed id, nor how errors surface. 'GraphQL query project' is an implementation detail rather than behavioral context.

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?

Very short and front-loaded, which is good, but it is written as two terse fragments and the second one ('GraphQL query project') restates the operation and the transport without earning its place. Nothing is bloated, but the content per sentence is thin.

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 with no output schema, the description does mention the returned fields (name, status), which compensates a little. It still omits not-found behavior and whether additional fields are available, leaving the agent with only a minimum viable picture of a simple 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?

With a single parameter at 100% schema description coverage, the schema (type string, 1-64 chars) already carries the semantics. The description only restates 'by id' and adds no format, source, or lookup guidance beyond it, 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 resource and scope: a single time-tracking project fetched by id, with the fields it returns (name, status). The word 'One' implicitly contrasts with the sibling kiwihr_list_projects, so an agent can tell single-fetch from list without opening the schema, though the sibling is never named.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as kiwihr_list_projects (search/unknown id) or kiwihr_update_project. The only hint is 'by id', which merely implies the caller must already have an identifier.

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