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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value beyond that by disclosing the exact-match lookup semantics and the not-found outcome, though it does not discuss lookup cost or any partial-match behavior.

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, no filler, with the primary use case front-loaded and the exclusion last. Every clause earns its place.

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-parameter read tool with annotations covering the safety profile and an output schema covering the return shape, the description supplies everything else an agent needs: exact-match selection, the returned fields, and the not-found case.

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 parameter is fully documented ('Exact project id or name'), so the schema carries the burden. The description's phrase 'selected by its exact name or identifier' reinforces the same idea with no added syntax, format, or ambiguity guidance, so 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 verb and resource: 'read metadata for one Imagelato image project selected by its exact name or identifier.' It also names the shape of the identifier (exact name or id) and explicitly excludes a nearby sibling use case ('Not for a quick look at its latest processed images'), so an agent can separate it from list_projects and show_project_overview without opening a schema.

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?

Gives a clear trigger ('Use this when the user wants to read metadata for one project') and a negative condition ('Not for a quick look at its latest processed images'). The alternative tool is only implied rather than named, so routing is clear but not fully explicit.

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