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

With no annotations, the description does substantial work: it identifies Wikidata and Wikipedia as sources, states that this is a paid read, explains that invalid input, not-found, and upstream errors cancel settlement, and lists exclusions. It still does not cover rate limits or explicit error-response behavior beyond settlement cancellation.

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 front-loaded and organized into three functional parts: purpose and returned fields, explicit exclusions, and payment behavior. It is efficient overall, though the long colon-delimited field list is somewhat dense.

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?

Because there is no output schema, it is important that the description enumerates returned fields, exclusions, sources, and payment behavior, and it does so. The remaining gap is that it does not clarify how to choose between id and name or what happens when neither is supplied, despite zero required parameters.

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 schema already documents id, name, and paymentSignature. The description adds no parameter-specific meaning beyond the schema, so the baseline score 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 opening names the resource clearly: a professional profile of a notable person, with examples of person types and an explicit list of returned fields. It does not explicitly distinguish itself from sibling tools like entity_search or entity_company, so sibling differentiation is left to inference.

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?

It gives implied usage context by scoping the tool to founders, executives, and public figures, and it warns that family, residence, and full birth dates are not returned. However, it does not name an alternative tool or give explicit when-to-use versus when-not-to-use guidance.

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