get_monitor_summary

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

Declares 'pure read; no side effects' and notes the result is dynamic (may change if displays change). This compensates for the lack of annotations.

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?

Concise and well-structured with clear sections for usage, alternatives, and behavior. Every sentence adds value without redundancy.

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 zero parameters and existence of an output schema, the description fully covers purpose, usage, behavior, and return fields. No gaps.

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?

Tool has no parameters; input schema is empty with 100% coverage. Baseline is 4 per guidelines. Description does not need to add param info but indirectly adds value by explaining output.

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 lists connected displays with specific metadata (resolution, scaling, active monitor). It distinguishes itself from sibling tools like get_screenshot by focusing on metadata vs. capture.

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 explicit 'USE WHEN' scenarios (e.g., before get_screenshot to target a monitor) and 'NOT FOR' (capturing pixels), plus names get_screenshot as alternative.

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