Get client profile report

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

Annotations already declare readOnlyHint and idempotentHint, so the read-only nature is clear. The description adds 'recent' context but does not elaborate on consistency, freshness, or any other behavioral traits. With annotations covering safety, the description provides minimal additional value.

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?

One sentence of 13 words, very concise. However, it sacrifices informative content for brevity. Could be restructured to add key details without becoming verbose.

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 5 parameters, no output schema, and sibling tools, the description is too brief. It does not explain the output format, what 'recent' means, or how the parameters affect the report. The annotations help but the description alone is incomplete for effective tool selection.

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 has no property descriptions (0% coverage). The description mentions 'cargo, lead, and order-form' which hints at the boolean parameters, but does not explicitly clarify their meanings or the purpose of the 'limit' parameter. The description partially compensates but leaves gaps.

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 clearly states the tool gets one client profile and includes recent cargo, lead, and order-form report context. It distinguishes from siblings like limu_get_client (basic client info) and list tools, but does not explicitly differentiate from limu_get_client or explain what the profile report contains versus a simple client retrieval.

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 guidance on when to use this tool versus alternatives like limu_get_client, limu_get_lead_report, or limu_get_order_form_report. The description does not mention prerequisites, use cases, or exclusions.

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