freelance_get_my_profile

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

No annotations are provided, so the description must carry the burden. It discloses that it returns owner-only fields (email, listing status) and requires the READ_OWN permission. It also clarifies that it acts on behalf of the token's identity, which is a key behavioral trait. While it doesn't mention rate limits or response format, the critical aspects are covered.

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, efficiently structured. The first sentence states the purpose and key fields; the second provides usage guidance. No fluff, and the most important information (what it returns) is front-loaded.

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 zero-parameter tool with no output schema, the description provides all necessary context: what it returns, the permission required, and when to use it. It is fully sufficient for an agent to call it correctly and interpret the result.

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 tool has zero parameters and the schema is empty with 100% coverage, so there is nothing to explain. The baseline for 0 parameters is 4, and the description adds no parameter-related details because none are needed.

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 verb 'get' and the resource 'my profile' (the freelancer profile of the authenticated token). It distinguishes itself from sibling tools like freelance_get_profile by specifying it returns the profile belonging to the account the token authenticates as, including owner-only fields. This makes it 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?

Explicitly instructs to use this tool first to confirm which account and organization the token is acting for, and notes that every other tool acts as this identity with no argument to redirect. This provides clear when-to-use context and implicitly explains why alternatives like freelance_get_profile (which likely targets arbitrary profiles) are not appropriate for identity confirmation.

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