Freelance Prospection Guide — 7 Strategies to Find & Convert Clients

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

Annotations already declare readOnlyHint and idempotentHint, indicating a safe, read-only operation. The description adds no behavioral context beyond 'Get' (retrieval) and does not describe response structure, side effects, or any special handling. It does not contradict annotations, but adds little beyond them.

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 consists of a concise core statement followed by a necessary list of trigger phrases. It is front-loaded with the primary purpose, and the trigger list serves a clear routing function. It is longer than minimal but each element earns its place, and there is no fluff.

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 (two optional parameters, no output schema, read-only annotations), the description fully covers what the agent needs: what the tool returns and when to use it. No missing information for correct invocation.

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?

Both parameters (lang, response_format) are fully described in the schema with enums and defaults. The description adds no additional information about parameters and does not reference them. With 100% schema coverage, a baseline of 3 is appropriate.

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 opens with 'Get 7 proven prospection strategies for freelancers' and itemizes the specific strategies, making the resource and content explicit. The trigger phrase list further clarifies the domain. It clearly distinguishes from sibling guide tools (e.g., productivity tips, client management) by scope.

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 explicitly states 'Use when someone asks:' followed by 11 trigger phrases covering different languages and phrasings. This provides concrete conditions for invocation, though it does not name alternative tools or when not to use it, leaving some implicit differentiation.

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