mame_session_status

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

With no annotations, the description must disclose behavioral traits, but it only mentions 'live' and lists three status fields. It does not state whether the tool is read-only, what output format it returns, or how it behaves without an active session. This lack of disclosure could lead an agent to assume incorrect side effects or error handling.

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 entire description is a single nine-word sentence with a useful parenthetical. Every word contributes to conveying the core purpose, and there is no redundancy or filler.

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 tool has no parameters, but also lacks an output schema and annotations, placing the burden on the description. While the three listed fields provide some indication of the status content, the response format and edge-case behavior remain unspecified, making this minimally adequate rather than 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 input schema has zero properties, and the description does not introduce any parameter-related ambiguity. The baseline for zero parameters is 4, and no additional explanation is needed beyond what the schema already specifies.

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 defines the tool as providing 'Live session status' and lists three example fields: system, frame, paused. Although it lacks an explicit verb like 'get', the noun phrase implies retrieving current state, which is distinct from sibling tools that perform actions such as mame_pause or mame_session_stop.

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 offers no indications for when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or relationships to sibling tools. An agent would not know whether to prefer this over mame_capture_game_tick or run_lua_script for status queries.

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