List Money Movement Groups

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

Annotations indicate readOnlyHint=true, which the description does not contradict. The description adds minimal behavioral context by specifying '[1 API call]', hinting at a single request without pagination or rate limits, but it lacks details on output format, error handling, or other operational traits beyond the annotations.

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 extremely concise with two short phrases, front-loaded with the API call count and purpose. Every word contributes directly to the tool's functionality without unnecessary elaboration, making it efficient and well-structured.

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 simple input schema with one parameter and readOnlyHint annotation, the description is minimally adequate but lacks output details (no output schema provided) and deeper context like pagination or filtering options. It covers the basic purpose but could be more complete for a list operation.

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?

With 100% schema description coverage for the single parameter 'budget_id', the schema already fully documents it. The description does not add any extra meaning or clarification about the parameter, such as examples or constraints beyond the schema, so it meets the baseline for high 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 clearly states the action ('List all') and resource ('money movement groups for a budget'), providing a specific verb+resource combination. However, it does not explicitly distinguish this tool from sibling tools like 'list_money_movements' or 'get_month_money_movement_groups', which might have overlapping functionality, so it lacks sibling differentiation.

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, such as 'list_money_movements' or 'get_month_money_movement_groups'. It mentions the budget context but does not specify prerequisites, exclusions, or comparisons to other tools, leaving usage unclear.

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