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

Annotations only say readOnlyHint=true; the description goes further by disclosing the Owner/Admin permission requirement and enumerating the fields returned including the two distinct status values and confirmUrl semantics. That is behavioural context the structured data does not carry.

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?

Front-loaded with the core definition and exclusions before the return-value detail, and every clause is informative. Some sentences are heavily nested (the status/confirmUrl clause), which costs a little readability but no sentence is 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?

With no output schema, the description compensates by describing the returned fields and status values, and it covers the auth prerequisite and the exclusion rules. An agent has everything needed to call it and interpret the result.

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 projectId parameter is already documented as coming from fastero_list_projects, so the description adds nothing about parameter meaning. Baseline 3 applies when the 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?

Specific verb (List) plus resource (a project's open invites) with an explicit definition of what 'open' means — emailed-and-unaccepted plus requested-and-unconfirmed. It also names the exact boundary against accepted, cancelled and lapsed invites, so the agent can tell this apart from any cancel/mutation sibling.

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?

Gives two concrete use cases (fetching the inviteId that fastero_cancel_project_invite consumes, and checking whether a requested invite was confirmed and sent) plus an explicit exclusion list. The alternative tool is named with the condition that links the two.

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