clients_get

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral detail by specifying the returned data shape, including invoice summary statistics and a capped list of 10 recent invoices.

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 front-loaded sentence that states the operation and the returned content without filler. Every clause contributes to tool selection or expectation setting.

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 read-only get tool with two fully documented parameters and no output schema, the description provides enough context to select and invoke it. It explains the main return contents, though it does not describe error behavior when the UUID is not found or the full set of client fields returned.

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 both the required 'uuid' and optional 'companyId' parameters are already documented in the schema. The description reinforces that lookup is by UUID but does not add syntax, format, or meaning beyond what the schema provides, so the baseline of 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?

The description names a specific verb and resource ('Get detailed information about a specific client') and scopes it by UUID. It also enumerates what is returned (invoice summary statistics and the 10 most recent invoices), which clearly distinguishes it from list or mutation siblings such as clients_list and clients_update.

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 implies usage by stating that a specific client is fetched by UUID, but it does not explicitly contrast this tool with clients_list or state when not to use it. The intended use is inferable, but there is no explicit routing guidance.

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