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

The description discloses that only catalog names, prices, durations, and edit times are returned, and explicitly excludes patient treatment data and record identifiers. It also mentions bounded pagination. This goes beyond annotations by specifying the exact data scope and pagination behavior, giving the agent essential context.

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 two sentences with no wasted words. It leads with the primary function, then clarifies what is included and excluded. Each sentence adds value.

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?

The description covers the resource, pagination, and data scope. Since an output schema exists, return format is defined. It doesn't describe authentication or error cases, but those are not necessary for a read-only list operation. It is sufficient for an agent to call it correctly.

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?

The input schema documents cursor and clinicId with descriptions, but limit lacks a description. The description does not elaborate on parameter usage beyond mentioning bounded pagination, which implicitly relates to limit and cursor. With 67% schema coverage, the description does not compensate for the missing limit description, so it stays at 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 clearly states the tool lists the authenticated user's procedure catalog, specifying the resource and operation. It distinguishes from siblings by focusing on procedures, not clinics or events. The verb 'list' is precise and the scope is unambiguous.

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?

The description provides clear context that this tool retrieves the procedure catalog, which is distinct from sibling tools like get_clinic or list_clinics. However, it does not explicitly exclude other tools or state when not to use it, so it lacks explicit alternative routing. Thus a 4.

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