enrich_person_picture

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

The annotations already communicate that this is a read-only, open-world operation, so the description does not need to restate that. It adds a useful detail about cost ('Cost: 0 credits') and clarifies the output is a URL, but it does not disclose failure behavior, data source assumptions, or input validation expectations. No contradiction 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 two short, front-loaded sentences with no filler or redundancy. It states the purpose immediately and includes the cost detail without bloating the text.

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 simple read-only tool with one documented parameter, the description is mostly sufficient: it names the operation, the input, and the output type. It lacks brief usage or limitation context, but given the low complexity and strong schema/annotation coverage, it is reasonably complete.

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 schema already documents person_profile_url with the description 'Professional network profile URL,' giving 100% coverage. The tool description adds no additional parameter semantics such as expected URL format, domain restrictions, or validation rules, so it stays at the baseline.

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: 'Get the profile picture URL of a person.' It uses a specific verb and resource and explicitly identifies the return value as a URL, distinguishing it from sibling tools like enrich_person_profile or enrich_person_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?

No guidance is provided about when to use this tool versus alternatives. With many sibling person/company enrichment tools present, the agent gets no contextual direction about prerequisites, appropriate inputs, or cases where another tool would be more suitable.

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