show_flow

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

Discloses that the tool accesses stored data and returns entries. While no annotations exist, the description adequately covers the read-only nature and response structure. Could be improved by noting ordering or pagination, but it's sufficient for a simple list.

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 waste. First sentence defines the tool's core function and data shape. Second sentence clarifies parameter behavior and directs to an alternative for trends. Perfectly front-loaded.

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 no output schema, the description specifies the fields returned. It covers the single optional parameter and its effect. No additional context is needed for a simple retrieval tool.

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?

With 100% schema coverage, the baseline is 3. The description adds value by explaining the default behavior (all periods) and the format for filtering ('YYYY-MM'), going beyond the schema's bare description of 'Period filter'.

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 clearly states the tool returns monthly cash flow entries with specific fields (type, sub_type, category, amount, date). It distinguishes itself from sibling report_flow by specifying that show_flow returns raw entries rather than aggregated trend data.

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 tells when to use this tool (for raw entries) and when not to ('for trend analysis use report_flow'). Also explains behavior with and without the period parameter.

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