get_summary

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core behavior (summarizing expenses by category for a month) but does not disclose details like whether the summary includes totals, counts, or only categories with expenses, nor does it mention what happens if no expenses exist.

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, front-loaded sentence that immediately conveys the tool's purpose and key qualifier (by category, for a specific month). It contains no fluff or redundant information.

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 the tool's simplicity (two required parameters, no output schema, no annotations), the description adequately conveys the tool's function and required inputs. It could be slightly more complete by specifying the return format or edge cases, but the core selection and invocation information is present.

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 description coverage is 100% with each parameter described in the schema. The description adds context by noting the summary is for a 'specific month', linking both year and month parameters to the tool's purpose, but it does not provide extra syntax or format details beyond the schema.

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 specifies the action (Get), the resource (summary of expenses), and the exact scope (by category for a specific month). It distinguishes this from sibling tools like get_expenses, which likely returns detailed expense records rather than an aggregated summary.

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 this tool is for obtaining an aggregated view by category for a month, but it does not explicitly mention when to use this over get_expenses or list any exclusions. Sibling tool names are present but not referenced in the description, so usage context is only implied.

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