pet_buddy

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

With no annotations, description fully carries burden. It details consequences of altering output: personality drift, species extinction from dex, breaking accumulator and affection token tracking. Also explains reaction is shaped by mood, stats, bond.

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 highly efficient sentences: first states action, second provides critical usage and consequence details. 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?

Despite no output schema, description tells agent to relay exact result, which is sufficient. It covers purpose, behavior, and consequences. Could be slightly improved by hinting at return format, but the instruction to relay exactly fills that gap.

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 exist and schema coverage is 100%. Description does not need to add param info; baseline for 0 params 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?

Description clearly states the action 'Pet the buddy' and explains it's an interaction that affects mood, stats, and bond. It distinguishes well from siblings like buddy_talk, deactivate_buddy_interact, etc., as none of those involve petting.

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?

Provides clear instruction to relay the exact result and warns against paraphrasing. Implicitly defines when to use (as part of streak-tracking minigame) but does not explicitly list when not to use or mention alternatives.

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