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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is carried by structured data. The description's only added behavior detail is what the summary contains (notes and ticket counts), which is modest value but real; it says nothing about response shape, aggregation period, or whether counts are lifetime or open-only.

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?

Two short fragments with no filler, and the resource-and-contents information is front-loaded. The trailing 'client / get_summary' largely restates the tool name, so it earns little, but the overall size is not wasteful.

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 single-parameter read-only lookup, the description tells the agent what comes back (notes and ticket counts), which is the main missing piece given there is no output schema. However, it does not say whether counts are scoped (open vs. all tickets), nor how a missing or unknown client_id behaves, so gaps remain.

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?

Only one parameter, client_id, and schema coverage is 100% with its own description, so the schema fully documents the input. The description adds no format, range, or lookup guidance beyond that, which is the baseline case for a single well-documented parameter.

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 is a noun fragment, 'A client's summary: notes and ticket counts,' with no verb, but it does name the resource and the two data categories returned. That is enough to tell it apart from vision_get_ticket and vision_get_dashboard_counts, though the phrasing is clipped rather than declarative.

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?

There is no statement of when to use this versus vision_search_clients or vision_get_dashboard_counts, and no prerequisites such as needing a valid client_id. The agent is left to infer usage entirely from the name and the one-line content hint.

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