enrich_role_lookup

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

Annotations already provide readOnlyHint: true and openWorldHint: true. The description adds cost information ('Cost: 3 credits') and clarifies the lookup behavior. It does not contradict annotations and provides additional context beyond the safe-read nature.

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 two sentences plus a cost note, front-loaded with the core purpose. Every word contributes value, with no redundancy.

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?

The tool has no output schema, so the description should clarify return values. It implies the result is the person holding the role, but does not specify whether it returns a list, profile details, or just contact information. While annotations cover safety, the missing output detail leaves some gaps for a lookup tool.

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% as each parameter has a description (e.g., 'Role to look up, e.g. ceo', 'Name of the company'). The description does not add further parameter details beyond what the schema already provides, so 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 clearly states the tool's function: 'Look up a person by their role at a company. Find who holds a specific title at a given company.' The verb 'look up' and resource 'person by role' are specific, and it distinguishes from sibling tools like enrich_person_lookup or enrich_company_lookup by focusing on role-based lookup.

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 the use case (when you need to find a person by title at a company) but does not explicitly contrast with alternatives such as enrich_person_lookup or enrich_employee_search. There is no explicit when/when-not guidance or mention of alternative tools.

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