list_private_links

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

No annotations are provided, so the description must carry the full burden. The description correctly identifies the operation as a list (read-like), but it does not disclose whether pagination, filtering, or authentication is required. Since it is a list operation, the lack of destructive hint is acceptable, but more detail on return format would help.

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?

The description is a single sentence of 8 words, which is very concise and front-loaded with the key action and resource. However, it could include a bit more context without becoming verbose.

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 an output schema present, the description does not need to explain return values. The description is minimal but adequate for a simple list operation with one parameter. However, it lacks any mention of the Enterprise scope or potential filtering, which would be useful for completeness.

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% (the single parameter 'event_type_id' is described as 'Event type ID' in the schema). The description adds no additional meaning beyond the schema, so baseline 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?

The description clearly states the tool will 'List private booking links for an event type', which is a specific verb ('List') and resource ('private booking links' for an event type). The parenthetical '(Enterprise)' disambiguates the scope, but it does not distinguish from siblings like 'create_private_link' or 'update_private_link', though those are clearly different operations.

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 provides no guidance on when to use this tool versus alternatives such as 'create_private_link', 'update_private_link', or 'delete_private_link'. It does not mention prerequisites (e.g., Enterprise plan required) or any context indicating when listing is appropriate.

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