get_client

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 discloses that by default it returns all sections and that 'include' can narrow the response. However, it does not mention permissions, rate limits, or any side effects, which limits transparency.

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 concise and front-loaded with the main purpose. Every sentence adds value, and the Args section provides necessary parameter details. It is well-structured for quick understanding.

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 existence of an output schema, the description adequately covers return behavior (full client object by default). It also provides context via siblings, making it clear when to use this tool. Minor omissions like error handling are acceptable for a single-fetch tool.

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?

With 0% schema description coverage, the description explains all three parameters: agency_id as 'HawkSoft agency ID', client_id as 'HawkSoft client number', and include listing possible sections (details, people, contacts, claims, policies, invoices). This adds significant meaning beyond the schema.

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 explicitly states 'Fetch full details for a single client', using a specific verb and resource. It distinguishes itself from the sibling 'get_clients_bulk' by focusing on a single client.

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 clearly indicates this tool is for a single client, implicitly contrasting with 'get_clients_bulk'. It also provides guidance on using 'include' to narrow responses and save bandwidth. No explicit exclusions are given, but the context is sufficient.

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