getMoneyMovements

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that the tool 'returns' data (implying read-only), but does not confirm side effects, authentication needs, rate limits, or pagination. The minimal description fails to provide sufficient transparency.

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 (4 words). While it is front-loaded, it lacks structure and omits important context that could be added without much length. It is borderline under-specified, earning a 3.

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 output schema, no annotations, and the existence of sibling tools that filter by month or group, the description does not provide enough context for an agent to understand what is returned or how this tool fits into the workflow. It is insufficiently complete.

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 parameter meaning is already documented. The description adds no extra context beyond what is in the schema. Baseline 3 is appropriate as no value is added beyond 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 states 'Returns all money movements,' which is a clear verb+resource. However, it does not distinguish from sibling tools like getMoneyMovementsByMonth or getMoneyMovementGroups. Without differentiation, an agent may select the wrong tool. Score 3 reflects adequate but not exceptional clarity.

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. For example, it doesn't mention that getMoneyMovementsByMonth is for filtered results. No exclusions or context are given, leaving the agent without decision support.

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