get_person

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

No annotations are provided, so the description carries the full burden. It reveals the return contents (roles, investments, news) but does not explicitly state that this is a read-only lookup, mention permissions, or describe failure modes. Acceptable for a simple getter but lacks richness.

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?

A single, front-loaded sentence with no filler. The verb and resource are stated immediately, and the content list is compact yet informative.

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 single-parameter getter with no output schema, the description adequately covers the inputs (UUID) and the outputs (roles, investments, news). It could add an explicit pointer to search_people for finding UUIDs, but this is a minor gap.

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%, so the schema fully documents the uuid parameter. The description's 'by UUID' adds no new meaning beyond the schema, and no additional format or source details are provided. Baseline 3 applies.

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 ('Get'), a target resource ('person detail'), the retrieval key ('by UUID'), and enumerates the returned sections ('roles, investments and news'). This clearly distinguishes it from sibling search tools like search_people.

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?

The 'by UUID' qualifier and the parameter description ('profile UUID from a list result') make it evident that this tool is used when a UUID is already known, typically after a list/search result. It does not explicitly name alternatives, but the intended usage context is clear.

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