Find Mobile Phone from LinkedIn Profile

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

Annotations declare readOnlyHint and openWorldHint, which are consistent. The description adds behavioral details: high cost of 150 credits, success-based charging, and the need for confirmation. No contradictions with annotations.

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 structured with a title, cost notice, usage instructions, and args list. It is somewhat verbose with repetition of the title, but each section adds useful information. Could be more concise but still clear.

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 no output schema, the description does not explain the return value format, whether multiple phones can be found, or error handling. For a simple tool with one parameter, it covers usage well but lacks output semantics.

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% and the description only restates the parameter name and purpose. No additional format, validation, or example beyond what the schema provides. Therefore, it meets the baseline but adds no extra semantic value.

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 finds a mobile phone from a LinkedIn profile URL. The verb 'find' and resource 'mobile phone' are explicit, and it distinguishes itself from sibling tools like derrick_find_email or derrick_find_gender.

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 instructions: announce cost in bold and wait for confirmation, explains chaining with search_linkedin_profile when only a name is given, and notes that the cost is charged only on success. This gives clear when-to-use and how-to-handle context.

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