resemble_get_detection

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

With no annotations, the description carries the full behavioral burden. 'Get' clearly signals a read operation, and the experts flag hints at scope behavior, but it does not disclose side effects, errors, or whether the return is a single object versus a list. This is adequate but not rich behavioral context.

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 short sentences, front-loaded with the core action and identifier, followed by the one parameter nuance worth calling out. No wasted words.

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 low-complexity getter with an output schema, this description is close to sufficient, but it leaves the relationship to siblings and the exact meaning of 'all completed Intelligence results' implicit. An agent can call it correctly but may not know when it is the right tool without additional inference.

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: 'by UUID' gives meaning to uuid, and the experts clause explains a real behavioral condition for that boolean. It could be more precise about the default behavior when experts is false, but both parameters have enough semantic grounding.

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 ('Get') with a clear resource ('deepfake detection result') and retrieval key ('UUID'). This distinguishes it from sibling tools like resemble_create_detection and resemble_get_detection_answer without needing to open their 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?

The description implies usage via 'by UUID' and gives one concrete condition ('Set experts=true for all completed Intelligence results'). However, it does not explicitly state when to prefer this tool over siblings such as resemble_get_detection_answer or how the returned result relates to a prior create/run operation.

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