get_wedding_dashboard

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that this is an 'overview' spanning invites/paper/planning progress, implying a read-only aggregate, but says nothing about auth requirements, scope, or whether it summarizes or returns raw lists.

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?

A single front-loaded sentence with the verb and resource first and the content areas in a compact parenthetical. Nothing is wasted, though the parenthetical is terse enough that 'paper' and 'planning progress' are left unexplained.

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 zero-param aggregate read with annotations covering safety and no output schema, the description is close to sufficient, but vague labels like 'paper' and 'planning progress' leave the agent guessing at what data actually comes back and how complete the overview is.

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 zero parameters, so the baseline is 4 and there is no schema surface the description could add to. Nothing in the description misrepresents the parameterless interface.

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 (wedding planning dashboard overview) and enumerates the content areas (invites, paper, planning progress). It reads as an aggregate summary tool, which distinguishes it in spirit from single-domain getters like get_budget or get_registry, though it never names a sibling to make that contrast explicit.

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?

No when-to-use guidance and no alternatives are mentioned. Among dozens of siblings (get_budget, get_registry, get_gift_tracker, get_wedding_settings) an agent gets no signal for when the dashboard is the right entry point rather than drilling into a specific domain.

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