gta-daily-checklist

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

The description indicates the tool is read-only and returns a list of tasks with payouts. While no annotations exist, the behavioral expectations are clear from the description.

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?

Single sentence, front-loaded with key terms, no wasted words. Highly efficient.

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 parameter-less tool, the description fully explains what the tool provides. Given no output schema exists, it sufficiently covers the return format.

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?

With no parameters, the description adds value by specifying the output: tasks, payouts, and running total. This goes beyond the empty 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?

The description clearly states it provides the optimal daily money routine, listing every daily-reset task with payout and running total. It distinguishes itself from siblings like 'gta-daily-collectibles' by focusing on money-making tasks.

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?

No explicit guidance on when to use this tool versus alternatives like 'gta-daily-collectibles' or 'gta-reset-times'. Usage is implied but not clearly contextualized.

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