gta-exotic-exports

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

No annotations are provided, so the description carries full burden. It discloses that the data is time-sensitive ('Today's'), which is important for behavioral expectations (not to use stale cached results). However, it does not mention any side effects (none expected), authentication requirements, or rate limits. The time-sensitivity disclosure is valuable, earning a 4.

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 a single, concise sentence that conveys the essential information (what the tool returns: today's list of 10 cars and a map). Every word earns its place, and the key information is front-loaded. No wasted verbiage.

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 of the tool (no parameters, no output schema), the description is fairly complete. It tells the user they will get a list of 10 cars and a map, specified as today's data. It does not elaborate on the format or structure of the output, but for a tool with this low complexity, it is adequate.

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 tool has zero parameters, so the schema coverage is effectively 100% (empty schema). The description does not need to explain parameters, and it adds value by describing the output content (list and map). Baseline for 0 parameters is 4.

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 clearly states that the tool provides 'Today's GTA Online Exotic Exports special-vehicle wanted list (the 10 cars to source for the Auto Shop) + map.' It specifies the resource (exotic exports wanted list) and scope (today's list, 10 cars). The verb is implicit but clear, and the tool is well-differentiated from siblings like gta-cayo-targets or gta-street-dealers.

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 does not explicitly state when to use this tool or when to avoid it in favor of alternatives. Usage is implied by the tool name and description ('exotic exports'), but no explicit guidance is given. For an agent to decide between similar tools, more context would be helpful.

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