creator_capture_viewport

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains the output format (PNG), that the image is visible to the model, and the default scaling behavior (long side to 1024), adding useful context. It does not mention error conditions or side effects, but capture is inherently read-only and the description is reasonably transparent.

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 two concise sentences that front-load the purpose and provide key default behavior with no filler. Every sentence earns its place.

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?

For a simple two-option capture tool with no annotations and no output schema, the description is adequately complete: it states the action, output format, model-visible return, and default scaling. Minor omissions (e.g., behavior when saving to an invalid path) are acceptable given the low complexity.

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 already describes both parameters fully (full boolean, path string), covering 100% of the schema semantics. The description supplements this by revealing the default scaling behavior (long side to 1024), which clarifies the effect of the 'full' parameter and adds value beyond the schema.

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 action ('Capture the current Inochi Creator viewport as a PNG') and notes the returned image is visible to the model. No sibling tool captures the viewport, so it is well-differentiated.

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 explicit when-to-use guidance or contrast with alternatives. The intended use is implied (visual inspection), but without exclusions or alternative mentions, it remains generic.

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