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

Annotations already declare readOnlyHint/no-destructive, and the description does not contradict them. It adds substantive behavior beyond annotations: the page is read-only, secrets are hidden, the link is immutable ('never changes'), and `shared: false` indicates absence of a link. That is meaningful context for a read call whose return content matters.

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 tightly-packed sentences, front-loaded with the core action and scoping semantics. The parenthetical is information-dense rather than wasteful, though the description is on the busier side.

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 return-value burden and does so: it lists what the link shows and who can open/was invited, plus the stable-link guarantee. Nothing an agent needs to call or interpret this tool is missing.

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%, so all four parameters (path, method, endpoint_id, collection_id) are already documented in the schema, including the method+path vs endpoint_id alternative. The description adds no per-parameter detail, so the baseline of 3 is appropriate.

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?

States a specific verb+resource ('Get the shareable link of an endpoint') and immediately clarifies what that link is (read-only page with docs, examples, latest run). It names the sibling 'share_api_endpoint' as the counterpart, so an agent can distinguish it from related sharing tools without opening a schema.

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?

Explains the use case ('put the link in a PR, an issue or a message') and clarifies the `shared: false` state with a pointer to share_api_endpoint. It gives clear positive context but no explicit when-not-to-use guidance.

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