passgage_list_branches

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

With no annotations, the description carries the full burden. It indicates read-only behavior through 'list' and mentions filtering/pagination, but does not disclose the return format, pagination metadata, or potential side effects. No additional behavioral context beyond the schema is 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?

The description is a single, front-loaded sentence that clearly conveys the purpose without any fluff or redundancy. It is appropriately sized given the tool's simplicity.

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?

The tool lacks an output schema and annotations, so the description should explain return values and edge cases. It does not describe the response structure, whether pagination metadata is included, or how to retrieve a single branch. This is a significant gap for an agent to fully understand the tool's behavior.

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 input schema covers 100% of parameters with descriptive definitions, including the Ransack-style filters example and pagination defaults. The description's phrase 'optional filtering and pagination' maps to the parameters but adds no meaning beyond what the schema already provides, meeting the baseline.

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' and the resource 'branches', which is specific and distinguishes it from sibling tools like 'get_branche' (single retrieval) and 'list_branch_groups' (a different resource). The mention of optional filtering and pagination further clarifies the scope.

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 implies this tool is used when you need to list branches, potentially with filters or pagination, but provides no explicit guidance on when to use it instead of alternatives like 'get_branche' for a single branch. There are no exclusions or alternative references.

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