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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description wisely spends its words elsewhere: it explains the schema-drift phenomenon that motivates the call and confirms 'takes no arguments and changes nothing.' That causal explanation is real context an agent cannot get from the annotations.

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?

Three sentences, front-loaded with the output (what it reports) before the trigger and the rationale. No sentence is padding — each adds either scope, trigger, or mechanism.

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?

No output schema exists, yet the description states what the caller learns (build identity and schema-match status), which is exactly the return-value information an agent needs. For a no-arg diagnostic tool this is fully sufficient.

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?

Zero parameters, so the baseline is 4. The description reinforces this with 'takes no arguments,' which removes any doubt about whether an empty object is required or a payload is expected.

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?

States a specific verb and resource — reporting the connector build and whether its advertised tool schemas match the live API. The resource is unmistakably distinct from the trip-planning CRUD siblings and from `whoami`, which concerns caller identity rather than connector contract.

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?

Gives a crisp, concrete trigger: call it when a tool rejects a field you expect to exist or accepts one with no effect. It supplies the causal rationale (clients cache schemas at connect time) so the agent understands why the trigger matters. It does not name when-not-to-call or point at a sibling alternative, so it stops short of a 5.

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