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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine value by disclosing the field set returned and the scope limitation that government identifiers are unavailable through this server, but says nothing about not-found behavior or permissions.

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?

Two compact sentences plus an endpoint reference, with the returned-field information front-loaded. The endpoint path is marginally redundant with the schema but earns its place as an API mapping hint.

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, the description usefully enumerates the returned fields and flags the government-identifier exclusion, which is exactly the kind of scope detail an agent needs. The main missing piece is disambiguation from get_employee/list_persons.

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% and the sole parameter person_id already carries a description ('Arcoro personId'). The description only echoes the path template GET /v1/Common/Persons/{personId}, adding no new meaning such as format or source of the ID.

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 resource (one Person record) and enumerates the returned fields (names, contact details, address, login username, security groups), which distinguishes it from the list_* siblings. However, it never clarifies how a 'Person' differs from an 'employee' despite exaktime_get_employee being a direct sibling, leaving a real ambiguity.

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?

There is no explicit statement of when to use this tool versus exaktime_list_persons or exaktime_get_employee; the single-record nature is only implied by 'One Person record'. No prerequisites or exclusion conditions are given.

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