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

Annotations already establish readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful context beyond those: the read is 'live,' the same content is served at web addresses listed in the door, and a URL fallback exists for clients that can open URLs. No contradiction with 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 tight sentences with no filler. The core instruction is front-loaded, and the fallback URL and catalog pointer each earn their place as practical guidance.

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 read-only tool with one optional enum parameter, the description covers the initial read, the detail-read usage, and fallback access. There is no output schema, so a little more detail about what the returned read looks like would help, but it is not a significant gap for this simple 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 fully documents the optional section parameter with an enum and description, so the baseline is 3. The description adds the practical guidance to omit it for the first read and choose it for detail, but it does not add deeper semantic detail about section values or response shape.

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 and resource: 'Read the live short city front door through this connector.' It further distinguishes the two call modes—omit section for the first read, or choose a section for detail—so an agent understands exactly what the tool produces.

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?

It gives clear context: omit the section for the required initial read and pass a section only when detail is needed. It also tells a lost agent to use this tool or the URL fallback, though it does not explicitly name sibling tools or state when not to use it.

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