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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real context beyond that: the manage-scope authorization limit and the fact that the returned destination feeds the budget and guest travel estimate tools, which is cross-tool behavior the agent cannot get from annotations.

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 dense sentence, front-loaded with what is returned and ending with the authorization constraint. Every clause carries information, though the run-on enumeration of every returned field is slightly heavy.

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?

With no output schema, the description carries the burden of describing return contents, and it does so comprehensively while also stating the authorization scope. Missing only explicit routing against sibling read tools, which is a minor gap for a simple single-parameter getter.

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% and the single wedding_id parameter is fully documented in the schema, including the multiple-weddings condition. The description adds no new syntax or format detail about the parameter, so the baseline 3 applies.

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 names a specific verb and resource ('Returns the signed-in account's selected wedding details') and enumerates the fields returned (partner names, date, location, venue, city/country, destination). It is clearly distinguishable from get_my_wedding_stats or get_venue_details, though it never names a sibling explicitly.

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?

Usage is implied rather than stated: it notes access is limited to weddings the account can manage and the schema notes wedding_id is required only with multiple weddings. There is no explicit guidance on when to prefer this over get_my_wedding_stats or get_venue_details, so an agent must infer the routing.

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