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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds non-obvious access control ('Only the owner or an admin can read it') and that the link is private. It does not say what happens when a member has no link yet or how failures surface, so it falls short of full behavioral disclosure.

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 short sentences, front-loaded with the action and resource, followed by the trigger and the permission caveat. Every sentence carries distinct information with no 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?

For a one-parameter read tool with annotations and no output schema, the description covers purpose, trigger, member identification, and authorization. Only minor gaps remain, such as behavior when the member has no existing link or is pending.

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% and the single parameter is documented as 'Member name or id (model_id / member_id)', so baseline is 3. The description goes further by defining what a 'member' can be (a creator or a production crew member) and pointing at list_models/list_crew to resolve the identifier, which meaningfully disambiguates an otherwise broad parameter.

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 and resource ('Get the private portal link') and immediately scopes the resource to two member kinds, naming list_models and list_crew as the ways to identify them. An agent can tell this apart from creation-side siblings like invite_member or create_crew_member without opening the 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?

Explicit trigger given: 'Use it when the user lost the link or wants to send it again.' No explicit when-not or alternative tool is named, but the trigger condition plus the permission constraint is enough to place the tool correctly in a workflow.

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