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

With no annotations, the description must carry the behavioral burden. It indicates this is a read-style operation by saying 'Resolve ... and return' and scopes to 'public' posts, but it never explicitly states that no data is modified, whether authentication is required, or how errors are surfaced. The transparency is adequate but not thorough.

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, front-loaded sentence that names the action, target, and return contents with no filler. Every phrase 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 two-parameter read tool, the description covers the input concept (identifier-based resolution) and the output categories, which is sufficient for basic invocation. It omits edge-case behavior such as not-found responses or content size limits, but these are less critical given the simple, public, non-mutating nature implied.

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?

The schema documents identifier thoroughly and include_content not at all (50% coverage). The description adds a minimal link by calling content 'optional machine-readable content', which hints at include_content, but does not clarify what enabling it yields or when it is appropriate. It compensates only partially for the schema 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?

The description clearly states a specific verb ('Resolve') and resource ('one public realization/gallery post') and enumerates the returned payload (metadata, evidence, media links, optional content). The word 'one' sharply distinguishes it from the sibling get_realizations, and the title reinforces the singular scope.

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 description implies the use case: you need details for a single realization/gallery post, as opposed to get_realizations which evidently lists them. It does not explicitly name alternatives or state when not to use it, but the singular scope and 'public' qualifier give the agent enough contextual signal to select it appropriately.

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