take_waveform_screenshot

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

With no annotations provided, the description carries the full burden. It discloses the return format ('PNG image') and intended consumer ('Claude can analyze'), but lacks disclosure of prerequisites, error states (e.g., window not open), or side effects.

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 efficient sentences with zero redundancy: first states the action, second states the return value. Every word earns its place and the description is appropriately front-loaded.

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 no output schema, the description adequately covers the essential contract (action and return type). However, for a media-generating tool without annotations, it could briefly mention prerequisites like simulator connection status.

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?

With zero parameters, the baseline score applies. The description requires no parameter clarification since the schema is empty, though it could have mentioned any implicit parameters like output path or quality settings if they existed.

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 specific action ('Capture a screenshot'), the target ('SimVision waveform window'), and distinguishes itself from siblings like waveform_add_signals or get_signal_value by focusing on visual capture rather than data manipulation or querying.

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?

While the purpose implies visual inspection use cases, there is no explicit guidance on when to use this versus alternatives like describe_signal or get_signal_value, nor are prerequisites (e.g., requiring a connected simulator) stated.

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