ofw_list_expenses

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

The description mentions pagination, which adds useful context beyond the readOnlyHint annotation. However, it lacks details on data freshness, sorting order, or what happens if pagination parameters are omitted.

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 a single sentence with no unnecessary words. It is concise and front-loaded with the main action.

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 no output schema and only two simple parameters. The description is sufficient for basic understanding but lacks details on return format, pagination indicators, or error handling.

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% with descriptions for both 'max' and 'start' parameters. The description does not add any extra meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 'List OurFamilyWizard expenses with pagination' clearly states the action (list) and resource (expenses). It is specific but does not explicitly distinguish itself from sibling tools like ofw_get_expense_totals or ofw_create_expense, though the function is inherently different.

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. There is no mention of prerequisites, ordering, or when to prefer it over other tools like ofw_get_expense_totals.

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