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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description still adds real value by disclosing that document contents are not retrieved and by naming the exact metadata fields returned, which no structured field provides. It does not mention paging behavior, but the schema covers that.

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?

Three terse fragments, front-loaded with the resource and its returned fields, then the scope limit, then the endpoint. No sentence is padding.

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 states the content limitation, and paging is fully specified in the schema. The only shortfall is that person_id's meaning/format is left entirely to the schema pattern.

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 67%: page and limit are documented in the schema, while person_id carries no description. The description's GET path '/people/{personId}/documents' partially compensates by showing person_id is a path identifier, but adds no format or constraint detail beyond the schema pattern, so the baseline 3 holds.

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?

Names a specific resource (documents on a person's record) and enumerates the returned fields (file name, type, size, upload status, download link), which lets an agent distinguish it from list_person_skills, list_person_tasks and the other person sub-lists. The explicit 'Contents are not read' further pins down what this tool is not.

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?

Usage is only implied: 'Contents are not read' signals this metadata listing is not the way to fetch a file's contents, but there is no statement of when to prefer it over get_person or the other person sub-list tools, and no prerequisites given.

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