everhour_get_client

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

With no annotations, the description carries the full burden. 'Get details' clearly implies a read-only operation, but it does not disclose any additional behavioral context such as response format, error handling, authentication requirements, or rate limits. It is minimal but not misleading, earning a borderline score.

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 sentence, front-loaded with the action and resource, efficiently communicates the tool's purpose. No redundancy or fluff; every word earns its place.

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 simple retrieval tool with one parameter and no output schema, the description is adequate. It tells the agent what it does and how to identify the client. However, it could be more complete by mentioning that it returns full client details or that the client must exist, but given the clarity of the operation, 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?

The input schema has 100% coverage with the parameter 'id' described as 'Client ID'. The description's 'by ID' adds little beyond the schema. It does not clarify that the ID must be numeric or that the client must exist, so it meets the baseline without exceeding 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 uses a specific verb ('Get'), identifies the resource ('details of a specific client'), and specifies the lookup method ('by ID'). This clearly distinguishes it from siblings like everhour_list_clients, which retrieves all clients.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention that this is for fetching a single client by ID, nor does it reference everhour_list_clients for listing all clients. The intended use is only implied by the tool's name and parameter.

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