edb_list_comments

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

Annotations already declare readOnlyHint=true and destructiveHint=false, setting clear behavioral expectations. The description adds minor value by noting that results are 'sorted' and returns a list of addresses with comments, but does not explain the sort order, format, or edge cases. Thus it adds some context but is not rich.

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 three sentences, each adding distinct information: purpose, detail about sorted output, and return type. It is mostly concise, but the final 'Returns: str: Comment listing' line is somewhat redundant with the preceding sentence. No wasted words overall.

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 listing tool with good annotations, the description is adequate but not fully complete. It omits details like sort order, confidence in completeness, and format of the output string. Given the output schema is declared present (but not provided), the description could still be more explicit.

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?

There are zero parameters, and schema description coverage is 100%. The description adds no parameter information, which is acceptable as none exist. It does not explicitly state that no arguments are required, but the schema already implies this.

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's purpose: 'List all address annotations added via edb_add_comment.' It uses a specific verb ('list') and resource ('address annotations/comments'), and uniquely identifies the tool among siblings like edb_add_comment and edb_list_bookmarks.

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 does not provide guidance on when to use this tool versus alternatives (e.g., edb_add_comment, edb_remove_comment, edb_list_bookmarks). It lacks explicit context or exclusions, leaving the agent to infer from the name alone.

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