penpot_list_comment_threads

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

No annotations provided. Describes read-only retrieval and return fields, but omits pagination, ordering, or error behavior. Adequate but gaps.

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 sentences: purpose then return details. No redundant words. 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?

Covers purpose, resource, and return structure. Missing pagination and error handling, but acceptable for a simple list tool with one param.

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 has 1 param fileId with 0% description coverage. Description mentions 'in a Penpot file' but doesn't further describe fileId beyond the name. Partially compensates but could add format or source info.

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?

Clearly states verb 'list' and resource 'comment threads in a Penpot file'. Distinct from siblings like create, resolve, delete comment threads. Specifies exact return fields.

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?

Implies usage for listing threads but no explicit when-to-use or when-not-to-use. No comparison with siblings like get_comments.

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