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

The description discloses key behavioral traits beyond annotations: read-only nature is covered by readOnlyHint, but the description adds that all monetary values are in major units and that the tool computes nontrivial logic (alert thresholds, headline priority). It does not describe pagination or return format, but with no output schema and readOnlyHint covering safety, this is a minor gap.

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 long sentence but is front-loaded with the core purpose and then adds detail and usage guidance. It is dense but every clause earns its place; no filler.

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 no-param, read-only tool with no output schema, the description provides enough context: what it returns, how it differs from run_read_query, and the monetary unit convention. It doesn't explain the return structure, but given the absence of an output schema, this is acceptable.

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?

Zero parameters, so baseline is 4. The description adds no parameter details because there are none to add, and it correctly avoids inventing any.

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 (get) and resource (yesterday's morning briefing) and enumerates the exact contents: net-worth change, budget alerts at >=80%, transaction/transfer/asset activity, and a prioritized headline. This is far more specific than sibling tools like get_net_worth or run_read_query, making the scope unambiguous.

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 the agent when to use this tool: 'what happened yesterday' / daily-digest style questions. It also names the alternative (composing from run_read_query) and explains why this tool is preferable - the alert thresholds and headline priority are not simple SQL.

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