Get Freelancer Profile

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only nature is covered. The description adds useful context beyond annotations by specifying that it returns a complete profile with overview, skills, earnings stats, and availability, and by noting the default-to-self behavior.

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 well-structured with a summary line, an Args section, and a Returns section. It is easy to scan and front-loads the core purpose. There is minor redundancy between the opening sentence and the Returns section, but overall it is appropriately sized.

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?

For a simple read-only getter with two optional parameters and no output schema, the description provides sufficient invocation details and return expectations. The only slight gap is ambiguity around whether user_id can fetch arbitrary users' profiles or only the authenticated user's, which could affect correct usage.

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 100%, so the schema already documents both parameters and their defaults. The description largely restates this information, with only a slight clarification that user_id defaults to 'your profile' rather than just 'the authenticated user', matching the schema but not adding substantial new meaning.

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 identifies the operation as retrieving profile information, using the specific verb 'Get'/'Retrieve' with the resource 'freelancer profile'. It lists the key data areas (title, skills, stats, availability), which distinguishes it from sibling tools like upwork_get_contract or upwork_get_connects.

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 implies when to use this tool: whenever you need the freelancer profile details. It also clarifies that user_id is optional and defaults to the authenticated user. However, it gives no explicit guidance about when not to use it or which alternative tool to choose (e.g., update_profile for modifying).

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