figma_get_console_logs

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

Annotations declare readOnlyHint=true. Description adds that it uses no CDP, default limit 50, and targeting options. No contradictions, and extra context provided.

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?

Three sentences, each adding distinct value: purpose, technical note (No CDP), and usage details. No fluff, 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?

Adequate for a read-only fetch with no required params. Missing output format description since no output schema, but not critical. Overall complete for 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?

Schema describes fileKey and figmaUrl, but description adds 'Limit default 50' and clarifies targeting for multiple plugins. Schema coverage 67%, but description compensates for limit parameter.

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?

Description clearly states 'Get plugin console logs (log/warn/error) from the F-MCP plugin buffer', specifying the verb, resource, and log types. It distinguishes from siblings like figma_clear_console and figma_watch_console.

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 guidance on when to use fileKey or figmaUrl for targeting specific files. However, it does not explicitly contrast with alternatives like figma_watch_console, though the purpose is clear.

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