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

Annotations already establish readOnly=true, destructive=false, and closed-world, so the safety profile is covered. The description adds a meaningful behavioral constraint ("Owner only") and clarifies that pending invitations are included, though it does not discuss pagination or failure behavior.

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 plus the "Owner only" restriction, with no filler; the returned fields are front-loaded. Structure is fragment-like but efficient.

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 one-parameter, read-only tool with rich annotations and an output schema, the description supplies the important missing context: the access scope and output composition. An agent has enough information to call it correctly without further prose.

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 single required parameter catalogId is fully described in the schema, including how to obtain it from list_catalogs. The description adds no parameter-level detail beyond the schema, so the high coverage baseline of 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 the resource (catalog shares) and enumerates exactly what is returned: owner plus shared users with email, name, role, and active/pending status. It does not explicitly say "list" or point to a sibling, so it is clear but not fully self-differentiating.

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 adds the authorization condition "Owner only," which is useful context for whether the agent may call it. It does not state when to choose this over siblings such as get_catalog or update_catalog, nor does it describe preconditions beyond ownership, so usage is only implied.

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