figma_watch_console

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

Annotations indicate read-only (consistent with streaming). Description adds behavior details: polling, timeout, default 30s. No contradiction. Adds value beyond annotations by explaining mechanism and timeout.

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 concise sentences, front-loaded with purpose, no filler. Each sentence adds value: purpose, mechanism, timeout default.

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 one-parameter tool with no output schema, the description covers purpose, mechanism, and timeout. Missing output format (streaming logs structure) but acceptable given simplicity.

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?

Schema coverage is 0%, so description must compensate. It mentions 'Timeout default 30s', explaining the timeoutSeconds parameter's default. However, it does not describe valid range or behavior at extremes. Provides minimal but adequate guidance.

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 streams plugin console logs until timeout, using the verb 'stream' and specific resource 'plugin console logs'. It distinguishes from siblings like figma_get_console_logs and figma_clear_console by indicating real-time polling behavior.

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?

Description implies usage for watching logs in real-time but does not explicitly state when to use or avoid this tool, nor does it mention alternatives like figma_get_console_logs. The context is clear, but exclusions or comparisons are absent.

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