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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered without prose. The description adds useful disclosure of what is returned (industries, intro requests remaining), but says nothing about the join_code parameter, caching, or when a profile might be absent.

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?

Two sentences, front-loaded with the action and its scope, then the field list, then the usage cue. No filler or redundancy; every clause carries information.

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?

There is no output schema, so the description must describe the return payload, and it does so concretely by listing the profile fields. The one gap is the unexplained join_code, whose conditional role ('when a new member saved their join answers in this conversation' only appears in the schema) is left unaddressed in the description.

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 there is a single optional parameter, so the schema already carries the burden and baseline 3 applies. The description never mentions join_code, which is the genuinely puzzling part of this tool's signature (why a read of my profile takes a sign-up code), so it adds no meaning beyond the schema.

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 ('Return the signed-in user's own Nepternship profile') and enumerates the fields returned, which lets an agent distinguish it from get_member or browse_directory at a glance. The 'own' qualifier is the decisive differentiator from sibling lookups.

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 says when to reach for it: 'Use this when the user asks about their own profile or settings.' That gives clear positive guidance, but there is no exclusion clause pointing to get_member for other people's profiles or to list_matches for matching data, so the boundary is inferred rather than stated.

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