get_profile

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

The description is adequate, stating it returns data. However, it does not disclose prerequisites (e.g., authentication via manual_login) or side effects (e.g., read-only). No annotations exist to supplement behavioral info.

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: first states action and return list, second provides usage guidance. No redundant information, front-loaded with key purpose.

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?

In the absence of an output schema, the description lists return fields, which is helpful. It explains the purpose and usage context. However, it does not cover error conditions or prerequisites, slightly reducing completeness.

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 the schema already describes the parameter. The tool description lists return fields (including those affected by the parameter) but does not add new meaning beyond the schema. Baseline 3 applies.

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 it retrieves the freelancer profile, stats, and connects balance, listing specific fields. This distinguishes it from siblings like update_profile (update) and submit_proposal (proposals).

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?

Provides explicit usage guidance: 'Use this to understand your current standing and available connects before bidding.' Implicitly suggests when to use (before bidding) but doesn't explicitly name alternatives or when not to use.

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