Get Monthly Summary

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds value by specifying the default month and listing the output categories (revenue, expenses, profit, etc.), which gives the agent a clear expectation of what is returned.

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 concise with two sentences in English and Spanish translation. It front-loads the key purpose and usage. Every sentence is informative with no waste.

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?

No output schema exists, so the description must explain return values. It lists specific financial categories (revenue, expenses, profit, tax liability, invoice stats, expense breakdown), providing sufficient detail for the agent to understand the output. Also mentions default month.

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% for the single optional parameter 'month'. The description reinforces the default month but does not add new information beyond the schema. Baseline 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 clearly states it retrieves a complete monthly financial summary, listing specific components (revenue, expenses, profit, etc.) and defaults to current month. This distinguishes it from sibling tools like get_quarterly_taxes or get_time_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?

Explicitly says 'Use this to answer questions about financial performance, cash flow, or monthly P&L.' This provides clear usage context, though it doesn't mention when not to use it or alternative tools. Given the sibling set, the guidance is sufficient.

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