openpanel_get_client

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

With no annotations provided, the description bears full responsibility for behavioral disclosure but only states the basic operation. It omits safety characteristics, error conditions if the client_id doesn't exist, or the structure of returned client details.

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 extremely brief, minimizing reading overhead, but the '[UNIFIED]' tag consumes space without adding value. The structure places the important information last after the metadata tag, which is suboptimal front-loading.

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 absence of an output schema and zero parameter descriptions, the description should explain what client details are returned. The current single-sentence description leaves critical gaps in the contract for a tool requiring three specific identifiers.

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 coverage is 0% with no descriptions for site, project_id, or client_id, yet the description provides no compensatory explanation. It fails to clarify whether 'site' refers to a domain name or internal identifier, or how these parameters form a composite key.

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?

'[UNIFIED] Get API client details' provides a clear verb and resource, but the '[UNIFIED]' prefix appears to be metadata noise. It fails to distinguish from sibling openpanel_list_clients or clarify that this retrieves a specific single client versus a collection.

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?

No when-to-use guidance is provided, nor are alternatives mentioned. The description does not explain when to use this singular retrieval versus openpanel_list_clients or how it relates to client management workflows.

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