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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. With no output schema present, the description steps in to disclose the returned information (connected yes/no, branch count, remediation hint), which is genuine value beyond the structured fields. It does not describe error or edge behavior, keeping it below a 5.

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?

A single sentence with no filler, and the three returned facts are ordered logically. It is phrased as a noun clause fragment rather than a directive, which is slightly less immediately scannable but costs no extra length.

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 one-optional-param read tool the description is close to sufficient, covering return content in lieu of an output schema. It omits the relationship to connect_timetable/disconnect_agent and does not say what counts as 'live' or how branch counts are scoped, which an agent acting on the result would want.

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%: the single optional 'brand' parameter is already documented with its slug source (get_overview brands[].slug) and the omission rule. The description adds no parameter-level meaning. Baseline 3 applies when the schema fully carries the burden.

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 resource (the Conciergr Timetable connection) and enumerates what the call returns: connection status, live branch count, and next-step guidance. It tells an agent this is a status/diagnostic read rather than a timetable dump, which the bare name 'get_timetable' would not convey. It stops short of distinguishing itself from close cousins like get_setup_status or connect_timetable.

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?

'What to do next if it isn't connected' implies this is a check performed before connecting, and implies connect_timetable as the follow-up, but the alternative is never named. No explicit when-not-to-use guidance (e.g., versus get_setup_status) is given. Usage is inferable but left to the agent.

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