billy_list_daybook_transactions

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

The description includes 'READ-ONLY', confirming non-destructive behavior. However, with no annotations provided, the description carries full burden but omits details about pagination, rate limits, or authentication requirements.

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?

Very concise—only two short phrases, front-loaded with the action. No wasted words, but could be slightly expanded to include parameter guidance without losing efficiency.

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?

Despite having 6 parameters with enums and ranges, no output schema, and no annotations, the description is minimal. It does not explain filtering, pagination, or the meaning of 'manual daybook transactions', leaving agents underinformed.

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 has no descriptions for any of the 6 parameters, and the tool description adds no parameter explanations. With 0% schema coverage, the description fails to compensate.

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?

Description clearly states the verb 'list', the resource 'manual daybook transactions (journal entries)', and explicitly marks it as 'READ-ONLY'. This differentiates it from sibling tools like billy_list_daybooks (lists daybooks) and billy_create_daybook_transaction (creates).

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?

No guidance on when to use this tool versus alternatives like other list tools. Does not mention prerequisites, suitable contexts, or when not to use.

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