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

Annotations declare a non-readonly, non-destructive, open-world, non-idempotent write, and the description goes well beyond that: it discloses the Nepternship account requirement, the fallback next step without an account, the join_code handoff from sign_up, and the failure modes (free limit reached, request already exists). No return format detail, but an output schema is absent and the description covers status reporting adequately.

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?

Purpose and call-to-action are front-loaded, and every sentence carries operational information (trigger, pre-call check, auth requirement, fallbacks). It is a dense run-on block, however, and could be split so the auth and error behavior is scannable rather than buried mid-paragraph.

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?

Covers what an agent needs to invoke this write tool safely: the account prerequisite, the join_code flow, the confirmation step, and the two known rejection reasons. The only material hole is the semantics of the required opportunity_id, which an agent must guess from the sibling tools' context.

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?

With 50% schema coverage the description must compensate, and it does for join_code (explains it comes from sign_up) and note (optional, 200-char limit, and a reminder to confirm with the user), while existing_member is only indirectly implied. The required opportunity_id — the one mandatory argument — is never explained in either schema or description, leaving the most important parameter undefined.

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 and resource ('Send a Nepternship member an introduction request') and immediately defines the concept — an intro/referral to a person the member can connect the user to, with a concrete example (analyst at JPMorgan). This clearly separates it from send_message and respond_to_request without requiring schema inspection.

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?

Explicitly names the triggering conditions and the sibling tools whose output feeds it (search_members, browse_directory, get_member), plus the UI path ('taps Request intro on the member card'). It also prescribes a pre-call step: check with the user whether they want to add a note before calling.

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