Get Money Movement Groups By Month

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds useful context about the batched re-allocation nature and the month-scoped behavior. The 'Read-only' phrase is redundant with annotations, but the additional domain context earns credit.

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 very short and front-loaded, packing the core purpose into the first sentence. However, the standalone 'Read-only.' sentence adds little value because it merely repeats the readOnlyHint annotation, so it does not fully earn its place.

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 has only two parameters, a 100% documented schema, rich annotations, and an output schema. The description explains what money movement groups are, that they are month-scoped, and how this tool relates to its sibling. Nothing essential for correct invocation is missing.

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 100%, so both month and budgetId are already documented in the input schema. The description does not add any parameter-specific details beyond what the schema provides, so baseline 3 applies.

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 uses a specific verb and resource: 'Get money movement groups' with the qualifier 'for one month', and adds the clarifying parenthetical 'batched budget re-allocations'. It also explicitly distinguishes the tool as 'the month-scoped view of list_money_movement_groups', making it easy to differentiate from its sibling.

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 clearly indicates the tool is for retrieving money movement groups for a single month and references list_money_movement_groups as the broader alternative. It does not explicitly state 'when not to use' or list other alternatives, but the context is clear enough for an agent to select this tool for month-scoped queries.

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