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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely useful context beyond that: the operation is a POST endpoint that is nonetheless a read-only search, which prevents an agent from mistaking the HTTP verb for a mutation. It also lists returned fields and the default page size.

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 dense but front-loaded, leading with what is searched and how filters combine, then covering return fields, pagination, and follow-up usage. Every sentence earns its place, including the clarification that the POST endpoint is read-only.

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?

With 11 optional parameters, no required fields, and no output schema, the description fills the key gaps: it summarizes returned fields, states the page size, explains filter combination, and points to sibling tools for retrieving a single CAPA. Nothing essential for correct invocation is missing.

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%, so the baseline is 3, but the description adds real value by stating that filters combine with AND, which is a parameter-interaction detail not captured in the schema. It also notes the 50-per-page default. Slight ambiguity remains around the returned GUID Id versus the numeric capa_id parameter, but the overall value exceeds the baseline.

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 names a specific verb (Search) and resource (corrective and preventive actions, including CAPA, SCAR, and CCAR), and it is clearly distinguished from the get-by-id sibling tools. An agent can tell exactly what this tool retrieves without opening the schema.

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?

It gives clear workflow guidance: use the returned Id with safetychain_get_capa and related tools, implying search first and then fetch details. It also explains that filters combine with AND. It stops short of explicitly naming when to prefer safetychain_search_records instead, so it is strong but not fully exclusionary.

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