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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint safety. The description adds meaningful context beyond annotations by clarifying the allowlisted-public scope and protected-route policy, as well as listing unavailable page types. This helps the agent set expectations about access constraints without being verbose.

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 only two sentences and front-loads the core behavior. Every clause earns its place: the resource, the markdown output, the allowlisting constraint, and the private-page exclusion. There is no redundant or filler wording.

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 parameter, a fully documented schema, rich annotations, and an output schema present, the description covers everything essential for correct invocation. It communicates the main usage constraint and the key limitation, so an agent can confidently decide whether and how to call the tool.

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 schema already fully documents the single path parameter with format and examples, giving a strong baseline. The description adds value by indicating that the path must correspond to an allowlisted public Vault page and that private pages are not valid targets, which is semantic information not present in the schema.

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 states a specific verb and resource: 'Returns a markdown representation of an allowlisted public Vitals Vault page.' It further distinguishes itself by explicitly excluding checkout, account, result, and other private pages. This makes the tool's purpose immediately clear and unique among the sibling 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 provides clear context about when to use this tool: for allowlisted public Vitals Vault pages under the protected-route policy. It also gives an explicit when-not by stating private pages like checkout, account, and result are unavailable. However, it does not name alternative sibling tools or describe when those should be used instead.

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