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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions 'Billing per call: 1 Credits' but does not state whether the call is read-only (likely, but not explicit), what happens if the username is invalid or not found, or any response format details. The safety and error profile are not addressed beyond the billing note.

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?

The description is concise, with a single sentence containing the core action and two additional pieces of metadata (group and billing). It is front-loaded with the essential purpose and adds no fluff. However, it lacks structured subsections, which is acceptable for a tool this simple.

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?

Given the tool's simplicity (one parameter, no output schema), the description might suffice for basic invocation, but it omits critical context such as the return value (a URN string), error conditions, and relationship to other profile endpoints. For instance, it doesn't explain that this URN is often a required input for other profile tools. The description is incomplete for an agent that needs to compose workflows.

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 description coverage is 0%, so the description must compensate. It only says 'by username', which reiterates the parameter name without adding format, requiredness, or example-based guidance (though the schema provides an example). The description does not clarify if the username is a LinkedIn profile URL slug, email, or other form, leaving ambiguity for the agent.

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 'Get urn of profile by username' clearly states the action (Get) and the resource (urn of profile) with a specific lookup key (username). This distinguishes it from sibling profile tools like profile_about or profile_details, none of which mention URN retrieval. The verb-resource pairing is unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is the intended method for converting a username to a URN for subsequent API calls, nor does it cite any exclusions or alternative tools (e.g., universal name to ID for companies). The agent must infer usage solely from the name.

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