show_flow

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

No annotations provided; description details the retrieval behavior and period effect. Lacks mention of error handling or empty results, but core behavior is transparent.

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?

Two sentences, no fluff. First sentence defines purpose and output structure; second covers parameter behavior and alternative tool.

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 a simple tool with one optional parameter and no output schema, the description covers return fields, parameter effect, and provides a referral for advanced needs.

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 describes period as a filter with example; description adds meaning by specifying that absence returns all periods and presence restricts to one month (YYYY-MM format).

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 verb 'show' and resource 'stored monthly cash flow entries', specifies fields (income, expenses, type, etc.), and distinguishes from sibling tool report_flow.

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?

Explicitly explains behavior without period (returns all) and with period (returns specific month), and directs to report_flow for trend analysis, providing clear when-to-use and alternatives.

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