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

Annotations flag openWorldHint=true and destructiveHint=true, and the description adds the key behavioral consequence an agent needs: the link is public, anyone with it can see dishes and prices, and originals photos are excluded. It also implicitly explains the idempotentHint by noting it "returns the existing" link rather than minting duplicates. The gap is that it never says how to undo sharing (revoke_menu_share exists) or that sharing is externally observable and revocable, which matters for a destructive-hinted action.

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?

Three tight sentences, front-loaded with the trigger condition, followed by behavior and then the negative case. Nothing is redundant and the exposure caveat about photos is included without padding.

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?

An output schema exists, so return shape needn't be described; the description instead covers the facts an agent must know before sharing (public access, content scope, photos excluded). Completeness would be higher if it mentioned revocability given destructiveHint=true and the sibling revoke_menu_share.

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?

With one parameter at 100% schema description coverage, the schema already explains menuId fully. The phrase "one of their ChefBear menus" reinforces ownership scoping but adds no syntax or format detail beyond the schema, so 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?

"Creates, or returns the existing, public link for that menu" gives a specific verb (create/return link) plus the resource (a menu) and its access scope (public). This clearly separates it from get_menu (read) and get_shared_menu (consume a share) among the siblings.

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 states an explicit precondition ("only when the user explicitly asks to share one of their ChefBear menus or wants a link other people can open") and an explicit exclusion ("Don't call it to read or open a menu yourself"). It stops short of naming the sibling it should defer to for reading, but the context is unambiguous.

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