Brex MCP Server

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

With no annotations provided, the description carries full burden and discloses key behaviors: it's a read operation (implied by 'List'), supports filtering and pagination, and returns specific details. However, it misses important context like authentication needs, rate limits, error conditions, or whether it's safe for frequent use, leaving gaps for an agent.

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 appropriately sized with three sentences that are front-loaded: the first states the core purpose, the second adds key features, and the third specifies return details. There's minimal waste, though the second sentence could be slightly more structured (e.g., separating filtering and pagination).

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 no annotations and no output schema, the description is moderately complete: it covers purpose, basic behavior, and return content. However, for a tool with 3 parameters and no structured safety hints, it should ideally include more on permissions, error handling, or example usage to fully guide an agent.

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 description coverage is 100%, so the schema fully documents all 3 parameters. The description adds marginal value by mentioning filtering by 'status' (matching 'budget_program_status') and 'pagination' (hinting at 'cursor' and 'limit'), but doesn't provide additional syntax, format, or usage details beyond what's in the schema.

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 verb ('List') and resource ('budget program configurations') with specific purpose ('define automated budget assignment rules'), making the tool's function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_budget_program' (singular vs plural) or 'get_budgets', which might cause confusion about 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 usage through context ('Supports filtering by status and pagination'), suggesting when to use it for filtered listing. However, it lacks explicit guidance on when to choose this tool over similar siblings (e.g., 'get_budget_program' for a single program vs this for multiple), and no exclusions or alternatives are mentioned.

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