Get client

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds 'recent' for associated data but does not explain recency criteria or other behavioral traits. Minimal additional context beyond annotations.

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?

Single sentence of 19 words. Efficiently conveys the tool's purpose. Could be slightly improved by grouping related entities, but concise for the information provided.

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?

No output schema exists, but description does not hint at return format or structure. Does not explain 'recent' behavior or how parameters control included data. Significant gaps for a 12-parameter 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?

Schema description coverage is 0%, yet the description does not explain any of the 12 parameters (e.g., includeKyc, includeCargo). It merely lists associated data types without linking to include flags. No meaning added beyond parameter names and types in 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?

Description clearly states it retrieves a single client with many related entities (cargo, shipments, etc.). Title 'Get client' and verb 'Get' with resource 'one LIMU client' are specific. Distinguishes from siblings like 'limu_get_clients' for listing and 'limu_get_client_profile_report' for a report subset.

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 explicit guidance on when to use this tool versus alternatives like 'limu_get_client_profile_report' or 'limu_update_client'. Usage is implied for obtaining a full client summary, but no conditions or exclusions are stated.

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