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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety profile is covered. The description adds the breadth of the returned record via the field list, but says nothing about not-found behavior, whether name matching is fuzzy, or how lang affects the payload.

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, zero waste, lead sentence front-loads the what and the return contents, second sentence handles lookup input. Nothing redundant.

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?

With no output schema, listing the stored fields is the right compensation and it does that well. However, for a lookup tool with zero required parameters, it omits what happens when slug and name disagree, when neither resolves, and how the language parameter influences returned text.

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%, so all three parameters are documented in the schema; the description only restates the slug-or-name lookup option. No additional semantics about precedence when both slug and name are supplied, or default behavior when neither is given.

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 and resource ('Fetch every stored fact for one project') and enumerates the returned fields, which makes the scope (single, full record) clearly distinct from list_projects or compare_projects. It never names a sibling explicitly, 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: you call it when you need the full record for one known project. There is no guidance on when to prefer search_site or list_projects to resolve a project first, and no note on the slug-vs-name precedence beyond 'Used when the slug is unknown' in the schema.

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