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

The annotations already establish read-only and closed-world behavior; the description adds useful scope by listing what data is included and noting that answers link to sources. It does not cover edge cases such as ambiguous names, but the behavioral profile is well beyond the 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?

The field list is dense but front-loaded and relevant, since it previews the returned profile. The final sentence gives practical input routing without 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?

With no output schema, the description appropriately previews return values and source-link behavior. Inputs are fully covered by the schema, and the remaining gap around ambiguous names is minor.

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 coverage is 100%, so the city enum and restaurant name/slug parameter are already documented. The description adds only that the slug comes from find_restaurants, which is helpful but marginal given the schema's completeness.

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 that this returns a group-booking profile for one restaurant and enumerates the profile contents. It also distinguishes itself from find_restaurants by saying the restaurant identifier comes from that sibling tool.

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?

It gives clear routing guidance: pass a restaurant name or the group_profile slug returned by find_restaurants. It does not explicitly state when not to use it, but the intended use case is clear enough.

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