detect_ai_media

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

With no annotations, the description fails to disclose key behaviors like required permissions, file size limits, or whether the call is read-only. It only states 'Returns the raw SongCheck assessment' without explaining what that means.

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 sentences with no wasted words. Purpose, input format, and output are front-loaded, making it easy to scan. Every sentence adds essential information.

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?

Given the simplicity (1 param, no output schema or annotations), the description covers purpose, input, and return type adequately. It lacks details on error handling or output structure but is sufficient for basic 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 provides no description for the single parameter (0% coverage). Description compensates by clarifying file_path must be absolute, local, and with specific extensions (.jpg/.png/.webp/.mp4/.mov), adding significant meaning beyond 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?

Description clearly states the tool detects if an IMAGE or VIDEO file is AI-generated. It specifies supported formats (jpg/png/webp for images, mp4/mov for videos) and distinguishes from sibling 'detect_ai_music', leaving no ambiguity.

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?

Explicitly instructs to pass an absolute path to a local file and lists acceptable formats. While it doesn't mention when not to use (e.g., for audio or remote files), the context is clear enough for most use cases.

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