gta-daily-collectibles

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

Describes behavior: fetches live data from gtaweb, falls back to reference table, mentions tunables freshness. No annotations provided, so description carries full burden; adequately covers read-only nature and edge case.

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 sentences, front-loaded with purpose, concise with 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?

Covers purpose, data source, fallback. No output schema, but for a simple no-param tool, it is complete enough. Could mention output format briefly.

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?

No parameters; schema coverage 100% trivially. Description does not need to add param info, but baseline 4 is appropriate.

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?

Clearly states it returns today's daily collectible income with per-day reward table and tunables freshness, distinguishing it from sibling tools like gta-daily-checklist and gta-collectible-locations.

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?

Implies use for current daily income data, mentions live source and fallback, but doesn't explicitly state when not to use or compare to alternatives. Still clear context.

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