mister_system_info

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

No annotations provided; description discloses return contents and a specific quirk (floppy cores need OSD reset). However, it does not explicitly state whether the operation is read-only or has side effects, leaving behavioral transparency partially incomplete.

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?

Description is appropriately front-loaded with 'IMPORTANT' and each sentence adds value. Slightly verbose but justified by the need to emphasize prerequisite use and detailed output.

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?

Given no output schema, the description provides a good overview of return items (file formats, keyboard mappings, launch behavior, OSD structure). Lacks specifics on output format but is adequate for the tool's purpose.

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?

Schema coverage is 100% with parameter description 'System name (e.g. 'PC8801', 'SNES', 'Genesis')'. The description adds no further meaning beyond the schema, so baseline score applies.

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 returns detailed system information including supported file formats, keyboard mapping notes, launch behavior, and OSD menu structure. It distinguishes itself from siblings by being a prerequisite for other operations.

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?

Explicitly states 'Always call this tool FIRST before launching games, navigating OSD, or interacting with any core.' Provides clear when-to-use guidance and implies it should precede sibling tools.

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