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

Annotations already declare it read-only, idempotent, and non-destructive, so the safety bar is covered. The description adds non-obvious behavior: a hard cap of 30 results, no pagination, empty-q returning an empty list, and the fact that it returns joined/pending/other alliance relationships.

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?

Single dense sentence that front-loads the login/permission requirement before the search semantics and result behavior. Information-dense with little waste, though the packed run-on style reduces readability slightly.

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 usefully discloses return content (relationship statuses) and result-limit/pagination behavior. The main gap is the unexplained required allianceId parameter.

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 0%, so the description must compensate. It clarifies q behaves as a name search and that an empty q yields an empty list, but it never explains the required allianceId, leaving half the parameters undocumented.

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+resource: search organizations by name as invitation candidates within an alliance. It clearly scopes the operation to alliance invitation discovery, though it does not explicitly distinguish itself from the sibling search_organization_invite_candidates.

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 concrete prerequisites (login required, alliance manage permission) and the downstream workflow (check details, then confirm invite). It does not name an alternative tool to use instead, so it falls short of explicit when-not guidance.

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