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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds a useful behavioral guarantee—that no provenance is fabricated and only genuine published records are reported—which gives the agent confidence in result authenticity. However, it does not describe return format, error behavior, or handling of missing/unknown mediaIds.

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?

The description is a single sentence with no filler or unnecessary detail. The main purpose is front-loaded, and the second clause reinforces a key reliability guarantee. It is concise, though it sacrifices helpful context for brevity.

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 tool with no output schema and no parameter descriptions, the description is too thin to be fully complete. It fails to explain what the returned provenance records look like, whether mediaId is required, or when this tool should be preferred over sibling tools. The authenticity guarantee is nice but does not fill these operational gaps.

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 compensate by explaining the parameter. It does not mention mediaId at all. The schema only provides type and length constraints, which is insufficient when the description itself adds zero parameter meaning.

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 uses a specific verb ('Report') and resource ('genuine published provenance records'), clearly indicating the tool retrieves provenance data for media. It goes beyond a tautology by stating the scope and authenticity guarantee. However, it does not explicitly differentiate this tool from sibling tools or mention the mediaId input.

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 provides no guidance on when to use this tool versus alternatives such as get_public_evidence or get_timeline_context. There is no stated context, prerequisite, or exclusion. This is a clear 'no guidance' case.

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