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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description is consistent with that. It adds substantial behavior beyond the annotations: cross-company appointment history, the null semantics of `disqualifications`, the name+birth-month matching method, the ambiguity rule when two register entries collide, and the explicit caveat that a match is an identity signal not a determination. It does not cover error behavior for an unknown ID or response/pagination shape.

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 first two sentences are well front-loaded, but roughly three-quarters of the text is a single sprawling sentence about one sub-field of the response, dense with semicolons and parentheticals. The information is defensible given there is no output schema, yet it is disproportionate to the tool's one-parameter surface and would benefit from breaking into shorter, structured statements.

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?

With no output schema and only one parameter, the description carries the documentation burden and largely meets it for the highest-risk field (`disqualifications`), including licensing provenance. It is weaker on the overall response shape — the composition of the appointment-history records and other person attributes are not described.

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 coverage is 100% for the single `id` parameter, so the schema baseline is already a 3. The description adds meaning by identifying the ID as Prometiam-internal and telling the agent to source it from company_detail or people_search, which is operationally useful beyond the schema text.

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?

States a specific verb and resource ("Fetch a single person (officer / director) by Prometiam internal ID") and names the return payload (full appointment history across all companies). This clearly distinguishes it from the sibling people_search, which is a search rather than a by-ID fetch.

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?

Gives concrete usage contexts (director-network analysis, counterparty due diligence) and, importantly, tells the agent where the required ID comes from: a company_detail or people_search response. It stops short of explicit when-not-to-use or alternatives for bulk/name-based lookups, so it is not a full 5.

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