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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world behavior, so the safety profile is fully covered. The description adds the scope of linked resources returned, which is useful, but says nothing about not-found handling or whether 'canonical' filters out non-canonical records.

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?

One front-loaded sentence with verb and resource first and zero padding. Slightly compressed by the ambiguous term 'canonical', which is never defined.

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 single-identifier read tool with an output schema handling return values and annotations handling safety, the description covers purpose and the linked-resource scope adequately. It would be complete with a note on what 'canonical' excludes and the failure mode for an unknown slug.

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%, so the burden falls on the description, which never mentions the slug parameter at all. The parameter name is self-descriptive and the schema supplies a pattern, so the gap is mild rather than severe, but no added meaning is provided.

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 (Read) and resource (one canonical project) and enumerates the linked entities returned (essay, dossiers, license). This separates it from list/search siblings like search_projects and list_dossiers, though no sibling is named explicitly.

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 phrase 'one canonical project' implies a single-record fetch by identifier and contrasts implicitly with the search/list siblings, but there is no explicit statement of when to use this versus search_projects or get_artwork. Usage is implied rather than stated.

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