eight_fetch_person

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not mention side effects (e.g., read-only), authentication requirements, error handling, or what happens for invalid ids. This is a significant gap for a fetch operation.

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 a single sentence that conveys essential information efficiently. It is appropriately sized for a simple tool, though it could be slightly more structured (e.g., separate usage hint). No waste.

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?

Given the tool has one parameter and an output schema, the description covers the core purpose and id source. However, it lacks behavioral context (e.g., authentication, id validity) and does not leverage the output schema to explain return values (though not required). Adequate but with clear gaps.

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?

The schema has 0% description coverage, but the description adds meaning by specifying the id parameter is 'returned by eight_search_person'. This provides context beyond the bare schema, though further details (e.g., id format) would improve it.

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 description clearly states the tool fetches detailed contact/profile fields for an id from eight_search_person. It uses a specific verb ('Fetch') and resource ('contact/profile fields'), and distinguishes from the sibling search tool by specifying the source of the id.

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 description indicates the tool should be used with an id returned by eight_search_person, providing clear context. However, it does not give explicit when-not-to-use scenarios or alternatives beyond the implied dependency on the search tool.

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