pressable_list_bash_bookmarks

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

With no annotations, the description carries the burden of disclosing behavioral traits. It merely states 'Get a list' without mentioning pagination, filtering, authentication, or return format. The presence of page and per_page parameters suggests pagination behavior, but the description does not surface this, leaving the agent without critical behavioral context.

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, concise sentence that states the core function without any filler. It is front-loaded with the action and resource, making it easy to parse quickly. Every word earns its place, and there is no unnecessary elaboration.

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 tool has three parameters, no output schema, and no annotations, the description is far too minimal to be complete. It does not explain pagination, search filtering, or what the response list contains. The absence of any mention of the return format or usage caveats leaves a significant gap for an agent trying to invoke the tool correctly.

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 only 33% (only 'search' has a description). The tool description adds no information about the 'page' or 'per_page' parameters, which are bare in the schema. It does not explain that these control pagination, nor does it clarify the search behavior beyond the schema's minimal description. The description fails to compensate for the low schema coverage.

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 starts with a specific verb 'Get a list' and clearly identifies the resource as 'Bash command bookmarks' scoped to 'your account'. This distinguishes it from sibling tools like pressable_get_bash_bookmark (singular) and pressable_create_bash_bookmark, making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that pressable_get_bash_bookmark should be used for retrieving a specific bookmark, nor does it clarify any prerequisites or exclusions. The usage context is only implied by the tool's name and resource type.

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