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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is free. The description adds genuine context beyond that: the external_id matching trick for correlating a request-creation with a creation once 'Alpha identity appears', and the access-scoped result set. It stops short of noting the 20-id batch cap or pagination 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?

Three front-loaded sentences with no filler: purpose, the non-obvious matching nuance, then the sequencing rule. The middle sentence is densely jargon-laden ('external_id', 'Alpha identity'), but it carries real information rather than padding.

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?

An output schema exists, so return structure is covered elsewhere, and annotations carry the safety profile. The description covers purpose, ordering, access scoping, and id-correlation semantics; only minor operational details (batch limit, empty/missing-id behavior) are left to the schema.

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 'ids' parameter is already documented in the schema with essentially the same wording the description reuses. The description adds no format, ordering, or batching detail (e.g. the maxItems of 20) beyond what the schema provides, 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 verb and resource ('Return sources and creations (project state)') plus the scope ('for one or more projects by id'). It explicitly differentiates from the closest sibling by noting that get-context 'lists projects without their sources/creations', so an agent can pick between them without opening either 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?

Names the prerequisite and ordering ('Use after get-context ... to load those projects' artifacts'), which is precisely the condition that selects this tool over the alternative. The access caveat ('Only projects you can access are returned') further constrains when it is useful.

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