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

The annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered elsewhere. The description's one real contribution is clarifying that data is recorded rather than live-fetched, which partly overlaps openWorldHint=false and adds little beyond it.

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 compact sentence with the capability front-loaded and the disambiguation as a trailing clause. No waste.

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 simple one-parameter read tool with rich annotations, this is close to sufficient. Without an output schema, though, the description could have said the result is a list of URL/state pairs, and it leaves the sole parameter undocumented.

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 0% and the description never mentions projectId, its required status, or the prj_ prefix format. The JSON pattern partially self-documents the format, but the description adds nothing to compensate for the coverage gap.

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+resource ('Read recorded project URLs and access state') and explicitly separates itself from a fetching operation, which helps against the sibling eurobase_get_url. It stops just short of 5 because 'access state' is left undefined, so the exact payload is still vague.

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?

The negative clause 'does not fetch URLs' implies this is the record-lookup counterpart to a live-fetch tool, but it never names eurobase_get_url or states when to prefer one over the other. Usage is inferable rather than guided.

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