List Invitation Links

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the quota cost of paging and that all_pages is bounded, but that same information already appears verbatim in the all_pages and max_items schema descriptions, so the added value over structured fields is limited.

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 terse sentences with the resource first and the quota constraint front-loaded before the paging caveat. Efficient, though the first sentence duplicates the title without adding information.

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 and seven parameters, the description is thin but the 100%-covered input schema and read-only annotations carry most of the burden. It never states what an invitation link record contains or how filtered results order, leaving a modest gap for a listing tool.

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 every parameter including name, status, account, and paging is already documented in the schema. The description adds no field-level meaning beyond what the schema provides, which is the expected baseline when schema does the work.

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 opens by restating the title ('List Invitation Links') and adds only 'Reads community data', which is a vague scope qualifier. The verb+resource is clear enough to distinguish it from create_invitation or delete_invitation_link, but it offers no differentiation from other list_* siblings beyond the resource noun already in the name.

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?

There is no statement of when to use this tool versus alternatives or what prerequisites exist. The all_pages note is a pagination caveat, not usage guidance, and no sibling is named for comparison.

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