ghl_snapshot_create_share_link

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds context beyond annotations by specifying the required token type (agency-level) and the POST endpoint. However, it does not disclose other behavioral traits like side effects or response 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?

Three sentences, front-loaded with the critical security constraint. The repetition of 'Create Snapshot Share Link' adds minor redundancy. Overall efficient and well-structured.

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?

No output schema and no description of the return value (e.g., what the share link contains or how to use it). For a creation tool that likely returns a link or object, this is a notable gap. Annotations partially compensate but the description is incomplete.

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 50% (companyId lacks description), but nested parameters in 'body' have descriptions. The description text adds no new meaning to parameters beyond what the schema provides. Baseline is 3 due to adequate schema coverage.

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?

Description explicitly states 'Create Snapshot Share Link' and 'Create a share link for snapshot', clearly identifying the action and resource. The tool name and sibling context (other snapshot ops like list, get pushes) further differentiate it. However, no explicit distinction from siblings is made in the description.

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 emphasizes the required agency-level token but provides no guidance on when to use this tool versus alternatives (e.g., other snapshot operations). No exclusions or when-not-to-use scenarios are mentioned.

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