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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds recency, Monday scope, and limit behavior, but it doesn't discuss ordering, authentication needs, or what fields are included in each summary. This is adequate but not deeply transparent.

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 compact and front-loaded: a clear one-line purpose followed by clear Args and Returns sections. Every sentence serves a purpose; there is no filler or repetition of schema fields beyond necessary semantics.

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 simple one-parameter, read-only list tool, the description supplies the resource type, recency, weekly cadence, and limit constraints. The only gap is the lack of detail on the internal fields of a weekly recap, which would be valuable since there is no output schema, but it doesn't block correct invocation.

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 0%, so the description must carry the parameter meaning. It fully does: 'limit: Maximum number of recaps to return (default: 5, max: 20)', which is precise and actionable for a single optional parameter.

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 verb and resource: 'Get recent weekly financial recaps (Monday summaries)'. It specifies the exact scope, is not a tautology, and is readily distinguishable from sibling gamification tools like get_gamification_summary or get_period_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 when to use it — when recent weekly recap summaries are needed — and clarifies their cadence ('Monday summaries'). However, it does not explicitly mention alternatives or state when not to use it, leaving the agent to infer selection context from the name and wording.

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