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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two real behavioral facts beyond that: the brief is immutable (retrieval cannot alter it) and user/client interpretations are kept distinct from verified source integrity, which tells the agent how to read 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, front-loaded with the action and resource, no filler. The second sentence is dense and jargon-heavy ('verified source integrity') but is not redundant 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?

With one parameter, rich annotations and an output schema, the definition covers purpose, ownership and immutability adequately. It still leaves the parameter's referent and any distinction from the closely named sibling getters unexplained.

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 description must carry the meaning of artifact_id, and it only contributes the word 'owned' as an ownership constraint. It never clarifies whether the id refers to the brief or the underlying artifact, nor any other constraint beyond the UUID format already in the schema.

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?

"Retrieve an owned immutable design brief and heat-map cells" gives a specific verb and resource, and the 'across conversations' phrase hints at scope. It never differentiates from siblings like get_design_draft, get_design_checkpoint or get_design_preview, so an agent cannot tell which 'get_*' returns what without opening schemas.

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?

"For continued design work across conversations" implies when the tool is appropriate, giving a weak situational cue. There is no explicit when-not guidance and no named alternative among the many sibling get_* design tools.

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