list_bookmarks

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

Annotations already declare readOnlyHint=true, so the description's mention of 'list' is consistent. The description adds no further behavioral context (e.g., pagination, rate limits, cursor usage). With annotations covering safety, the description provides minimal additional transparency.

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 a single sentence but includes the redundant phrase 'via API'. It could be more concise without losing meaning. Content is front-loaded with the key action and resource.

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?

Given the lack of output schema and a single undocumented parameter, the description should explain cursor and return structure. It fails to do so, making it incomplete for effective tool 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?

The single parameter 'cursor' has no description in the schema (0% coverage) and the tool description does not explain its purpose (likely pagination). This leaves the agent without crucial context for using the parameter correctly.

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 ('list all') and resource ('a user's Twitter bookmarks'), distinguishing it from sibling tools like 'search_bookmarks' which imply filtering. However, it does not explicitly specify that the bookmarks belong to the authenticated user.

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?

No explicit guidance on when to use this tool versus alternatives such as 'search_bookmarks' for filtered queries. The description implies it is for listing all bookmarks, but does not state when not to use it or provide alternative tool names.

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