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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond those flags: it defines the bounded scope, the aggregation window ('seven-day'), and an explicit privacy guarantee that no individual clinical or personal data is returned.

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 filler. The first sentence front-loads the verb, resource, and content categories; the second sentence is a compact but specific list of exclusions. Every clause contributes to selection and invocation decisions.

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 a single fully documented parameter and an output schema present, the description sufficiently defines what the tool returns and what it deliberately excludes. The only minor gap is not naming which sibling tool should be used when individual records are needed, but the negative boundary largely compensates.

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 description coverage is 100%, and the clinicId parameter is fully documented with a format pattern and description. The tool description does not add any additional semantic detail about clinicId, so the baseline of 3 is appropriate.

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 uses a specific verb ('Render') and names an exact resource ('bounded administrative overview for one tenant-owned Veterical clinic'), then enumerates the content categories: clinic metadata, seven-day schedule counts, provider and unassigned availability counts, and catalog previews. It also includes a strong negative boundary ('never returns individual appointments...'), which clearly separates it from the sibling detail/list tools.

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 makes the context clear: this is for an administrative overview and provides aggregate counts, not individual records. The explicit 'never returns' clause communicates a when-not-to-use signal, though it does not name sibling alternatives such as list_calendar_events or get_clinic_schedule_summary.

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