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

readOnlyHint=true already tells the agent this is a safe read, so the description's only job is to add context — and it adds none. It doesn't say whether answers are returned as raw key/value pairs, whether a client who hasn't filled the form returns empty or errors, or whether multiple submissions exist.

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 short fragment that wastes no words, but it is under-specified rather than concise — there is no front-loaded verb or scope statement to structure the agent's reading. Length itself is fine for a single-param read tool.

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-param read tool with no output schema, the description is the only place to explain what comes back, and it says nothing about shape, empty states, or how intake answers relate to the intake form. Annotations cover safety but not enough to make this complete.

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 100% and the single clientId param is documented in-schema with its source (list_clients), so the baseline of 3 applies. The description adds nothing about the identifier, but nothing is missing either.

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 phrase names a specific resource (a client's intake questionnaire answers), so an agent can infer it reads intake responses. But it is a bare noun phrase with no verb and no differentiation from close siblings like get_client_intake_form, get_checkin_answers, or list_clients_pending_intake, so the agent must guess which one returns the answers versus the form definition.

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 when-to-use guidance at all: no mention of prerequisites, no alternative tools, no conditions under which this is the right call versus get_client_intake_form or get_client_onboarding. Only the required clientId param in the schema hints at context.

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