gta-weekly-bonuses

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

With no annotations, the description carries the burden. It transparently discloses caching behavior ('cached per weekly window, serves stale data with a note if fetch fails'). This covers the key behavioral trait, though it omits potential details like response size or error format.

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 two sentences: the first clearly states the content, the second adds caching behavior. No extraneous information, and it is front-loaded with the core purpose.

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?

The description covers what the tool returns and its caching behavior, but it does not specify the output structure or format. Given no output schema, mentioning that the response includes specific fields would improve completeness, though for a simple fetch tool 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 input schema has no parameters, and schema description coverage is 100%. Since no parameters exist, the description cannot add parameter semantics beyond the schema, which is already complete. 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?

The description clearly states the tool retrieves the current week's GTA Online event from Rockstar Newswire, listing specific content like title, bonuses, podium vehicle, and discounts. This verb+resource structure distinguishes it from sibling tools that focus on other aspects (e.g., businesses, collectibles).

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 implies the tool is for weekly event data but provides no explicit guidance on when to use it versus alternatives like gta-tunables-status or gta-reset-times. No exclusions or when-not-to-use conditions are mentioned.

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