get_machine_status

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

No annotations are provided, so the description carries the full burden. It states the tool is for 'real-time' status, implying it's a read operation, but doesn't disclose behavioral traits like whether it requires specific permissions, rate limits, network latency effects, or error conditions (e.g., if machine is offline). For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the purpose and lists specific data points. Every word earns its place with no redundancy or fluff, making it highly concise and well-structured for quick understanding.

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 the complexity (real-time machine monitoring), no annotations, and no output schema, the description is incomplete. It lacks details on return format (e.g., structured data vs raw text), error handling, or operational constraints. For a tool that likely involves dynamic, time-sensitive data, more context is needed to ensure proper agent usage.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds no parameter information, which is appropriate. Baseline is 4 for zero parameters, as it doesn't need to compensate for any schema gaps.

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 'Get' and the resource 'real-time CNC machine status', specifying the exact data returned (position, state, feed rate, spindle speed, and overrides). It distinguishes from siblings like 'get_machine_settings' (likely static config) or 'get_gcode_state' (program state), though not explicitly. However, it doesn't fully differentiate from all siblings (e.g., 'get_system_info' might overlap), so it's not a perfect 5.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., machine must be powered on), exclusions (e.g., not for historical data), or compare to siblings like 'get_machine_settings' or 'get_system_info'. The context is implied (real-time status), but explicit usage rules are absent.

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