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

No annotations are provided, so the description carries the full burden. It mentions billing per call (1 credit), which is a behavioral trait, but it doesn't disclose what the response contains, whether it's read-only, or any rate limits. The description is minimal and doesn't add much beyond the name.

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 very concise (one sentence plus billing note). It's front-loaded with the core purpose. No wasted words, but it could be slightly more informative without losing conciseness.

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 has no output schema, no annotations, and a single parameter, the description should explain what 'complete work experience' includes (e.g., positions, dates, descriptions) and any limitations. It doesn't. The billing note is the only extra context. For a tool with such minimal structured metadata, this is insufficient.

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 schema has 1 parameter (urn) with 0% description coverage, but the description mentions 'by URN Group: Profile' which implies the urn parameter is a profile URN. The example in the schema provides a concrete format. The description adds minimal semantic value beyond the schema, but the schema itself is simple and self-explanatory.

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 clearly states the tool retrieves complete work experience for a profile identified by URN, which is specific and distinguishes it from sibling tools like get_api_v1_profile_about or get_api_v1_profile_education. However, it doesn't explicitly contrast with the similar 'get_api_v1_profile_full' sibling, so it's not a perfect 5.

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 doesn't mention that it's for full experience data specifically, nor does it exclude other profile-related tools. The billing note is useful but not usage guidance.

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