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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. Beyond that, the description adds a useful negative side-effect list ('does not upload media, attest rights, create checkout, charge, or start analysis') and identifies the return artifact as a tagged URL. This is meaningful context that goes beyond the annotations without contradicting them.

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 tight sentences with no fluff. The core action and return value are front-loaded, the use-case list is compact, and the negative constraints are delivered in one efficient clause. Nothing is repeated from the schema or annotations.

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 simple two-parameter tool, the description covers the intent categories, the return type, and side-effect negation. With no output schema, it would be more complete if it explained what 'tagged' means and what the 'source' parameter contributes, but the description is otherwise sufficient for basic correct invocation.

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. It does map the intent enum values to natural-language use cases ('surveillance' to 'surveillance review', 'compare' to 'recording comparison', etc.), which helps agents pick an intent. However, the 'source' parameter is completely undocumented, and the meaning of 'tagged' is never tied to parameters or behavior.

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 opens with a specific verb and resource: 'Return a tagged ForensiScope URL', then enumerates six concrete use cases (overflow, long-form analysis, surveillance review, recording comparison, incident timeline, pricing). It also differentiates itself from siblings by explicitly listing what it does not do: 'Does not upload media, attest rights, create checkout, charge, or start analysis.' This makes the tool's role clear and separable from classify_media_route and get_forensiscope_pricing.

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 gives clear context for when to use this tool by listing eligible intents and by stating non-actions that effectively say when not to use it. However, it never explicitly names alternatives or gives an exclusion like 'for classification use classify_media_route', so it stops short of a full 5.

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