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

With no annotations, the description carries the full burden and does add real behavior: it discloses the visibility model ('Members see only their own invitation'), the auth requirement ('Requires API key'), and an explicit prompt-injection warning that team purpose/names are untrusted data. It still omits return shape, ordering, and whether the result can be empty.

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?

Four short sentences, front-loaded with the primary action, with the safety and auth notes following. The untrusted-data sentence is slightly generic boilerplate for a zero-argument read, but it is defensible given the tool returns user-supplied names.

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 zero-parameter, read-only, no-output-schema tool, the description is close to sufficient: it covers what is returned (a shortlist plus invitations), who can see what, and the auth requirement. Only the absence of any note on result size/ordering keeps it from being complete.

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?

The schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly does not invent parameter talk for a parameterless call.

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 concrete verb ('Read') and resource ('private reusable team shortlist and invitations'), so an agent knows this is a read operation over team data. It implicitly contrasts with the mutate-style sibling manage_delivery_team, but never names it, and the mapping between the tool name ('delivery teams') and the described resource ('shortlist/invitations') takes a beat to reconcile.

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?

Usage is only implied: the word 'Read' plus 'private' suggests 'call this to see teams you already have'. There is no explicit when-to-use, no exclusion such as 'to create or edit a team, use manage_delivery_team', and no stated precondition beyond the API key requirement.

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