IvedaAI: Tracking

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds valuable response context (HTTP status, truncated/timedOut flags) beyond the structured annotations. It does not discuss auth or reversible effects, but the operation is simple and the annotations cover the safety profile.

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 compact and structured: a context line, a response note, and the endpoint with its parameters. No redundant sentences; the formatting is slightly telegraphic but clear.

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 single-endpoint tool with no output schema, the description covers the request structure and partial response conventions, but it does not detail success/error response bodies or the semantics of targetId. More explanation of what the operation returns would be needed for full completeness.

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 input schema only offers generic path/query/body objects, while the description names the actual parameters: cameraId in the path and targetId in the query, both integers. This is essential for correct invocation, though the semantic meaning of targetId is not explained.

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 names the exact endpoint and operation: 'PUT /api/cameras/{cameraId}/tracking — Set AI tracking target'. This gives a specific verb and resource, clearly distinguishing it from sibling tools like counting or detection.

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?

Usage is implied by the endpoint description ('Set AI tracking target'), but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions. The description does not mention any other IvedaAI operations that might overlap.

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