gta-business-set-state

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

No annotations are provided, so the description carries the burden. It mentions persistence and tracking of fill timers/cooldowns, which is positive. However, it doesn't explicitly state that setting 'sold' resets stock (though the schema does) or the effects of other fields. Behavioral traits are partially disclosed.

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, 40 words, front-loaded with key information. Every sentence adds value with no fluff or repetition.

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 the main purpose and persistence behavior. However, it omits mentioning the 'remove' functionality for stopping tracking, which is a significant use case. Without an output schema, the description should be more thorough about operations, but it's largely complete.

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 schema descriptions cover all parameters (100% coverage), so the description's mention of 'resupplied just now, sold just now, stock level, upgrades' adds minimal extra meaning. It provides context but doesn't enhance semantics beyond what schema already offers. Baseline 3 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 verb 'Record' and the resource 'GTA Online businesses', listing specific aspects (resupplied, sold, stock level, upgrades). It distinguishes from sibling tools like gta-business-status (read) by focusing on state recording and persistence.

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 usage after resupplying/selling but lacks explicit guidance on when to use this tool versus alternatives like gta-business-status for querying. No when-not-to-use or alternative tool names are mentioned.

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