budget_summary

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

readOnlyHint=true is consistent with 'Read', so no contradiction. The description contributes one genuinely useful behavioral constraint — the month must be 'completed' — but says nothing about what happens with an in-progress month, whether 'expected' versus actual figures are both returned, or the shape/magnitude of the response.

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?

A single front-loaded sentence with zero filler; the resource comes first and the period formats follow immediately. Nothing is repeated from the schema or annotations.

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?

For a one-parameter read-only tool with annotations covering safety and no output schema, the description does the essential work: it names the returned content and encodes the accepted input formats that the schema omits. It could be stronger by clarifying the 'expected' versus settled distinction and how a non-completed month is handled.

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 0% and the single parameter has no description or pattern, so the description must carry the semantics — and it does, giving both accepted formats (YYYY-MM-DD for a day, YYYY-MM for a month) plus the 'completed month' constraint. It stops short of noting timezone or validation/error behavior for malformed values.

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?

States a specific verb ('Read') and a specific resource ('expected pool balances and settlements'), scoped by period granularity. It implicitly distinguishes itself from mutation siblings like budget_settle and budget_record, but never names them, so the differentiation is inference rather than declaration.

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 implies when the tool applies (a single day or a completed month) but gives no explicit when-to-use or when-not-to-use guidance against siblings such as budget_status, which likely also reports balances. The 'completed month' qualifier hints at an exclusion (current/partial months) without stating what to do in that case.

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