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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one genuine behavioral fact beyond them: it performs no messaging or conversation initiation. It says nothing about return format, though for a zero-parameter info tool that gap is minor.

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 sentences, front-loaded with the core subject matter, and the negative boundary lands at the end where it is most useful. Some phrasing drifts toward promotional ('explore invitations to joint research and long-term human-AI relationships') and could be tightened.

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 parameters, no nested objects and no output schema, the description carries the full burden of explaining what comes back, and it does so at a topic level (participants, contributions, authority, invitations). Adequate for an informational tool, though it does not hint at the shape of the returned content.

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 tool takes zero parameters, so per the rubric the baseline is 4. The description introduces no parameter semantics to add, and none are needed.

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 names a specific resource (MAGNT's participants, their contributions and authority) and frames the tool as an informational lookup, distinguishing it from the messaging-oriented siblings via the closing boundary statement. It is clear enough to select, though 'MAGNT' itself is never defined for an agent that lacks prior context.

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: 'Learn when Alexander's capabilities may be useful' describes content, not a triggering condition. The one explicit boundary ('Does not send a message or start a conversation with ChatGPT') helps separate it from propose_contact and contribute_task_signal, but no sibling is named and no when-to-use condition is given.

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