IvedaAI: FaceMatch

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

Annotations already flag destructiveHint=true, and the description aligns by including a DELETE operation. It adds useful context about response JSON (status, truncated/timedOut flags) but does not disclose side effects of deletion, error handling, or authentication requirements.

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 dense yet well-structured, using indentation and clear labels for each endpoint. It front-loads the response note and operation list, and every line adds specific value without fluff.

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?

With four distinct operations and no output schema, the description gives a thorough parameter map and response flag explanation, but it lacks narrative on pagination behavior, error handling, or how to select among operations. It is a solid reference but not a complete operational guide.

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 generic schema is augmented by the description's detailed parameter lists, including types, required markers, and enums for each operation. This provides essential invocation details, though it does not explain the semantic meaning of parameters like 'scores' or 'nameContains'.

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 explicitly lists four endpoints with specific verbs (Get, Search, Delete, Latest) and resources (face matches), making the tool's purpose unambiguous. It clearly distinguishes FaceMatch operations from sibling tools like ivedaai_face and ivedaai_face_category by focusing solely on match-related operations.

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 or how to choose among the four operations. It lacks contextual cues such as 'use Search for filtering by attributes' or 'use Get match list when you have a faceKeyId'.

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