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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that this is a composite aggregate spanning several domains, which is useful behavioral context beyond the annotations. It does not disclose whether the data is summarized versus full records, or anything about size or cost of the call.

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?

Two short sentences with the scope front-loaded in 'The big picture of the wedding' and the routing hint placed last where it belongs. The middle list is dense but every item is informative; nothing is padded or redundant.

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 has to carry the burden of describing the return, and its enumeration of the six data domains does that adequately for a zero-parameter aggregate. Minor gaps remain around the shape of the returned counts and whether sections can be empty (e.g., no vendors yet), but overall an agent can call it confidently.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The enumerated contents do help the agent understand what the zero-arg call returns, which is a small bonus.

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 resource and enumerates exactly what the 'big picture' contains: date/days-to-go, moments with RSVP counts, guests, open and overdue tasks, budget and vendors. That is far more than a restatement of the title and lets an agent predict the payload. It does not explicitly distinguish itself from overlapping siblings such as get-budget, get-rsvp-summary or get-guest, so it stops short of a 5.

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?

'A good first call' is a real, if brief, usage directive that tells the agent to open with this tool for orientation. There is no when-not guidance and no named alternative for cases where the agent only needs one slice (budget, RSVP summary, tasks), so routing is left to inference from the sibling names.

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