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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds something annotations cannot: what information comes back (status, endpoints, capabilities), which is meaningful since no output schema exists. It still omits whether endpoints are live/authenticated or how fresh the status data is.

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 front-loaded sentence with no filler. The returned-content list is packed efficiently into the clause after the verb, and nothing needs to be trimmed or moved.

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 zero-parameter, no-output-schema read tool, the description must carry the burden of saying what comes back, and it does name three return categories. The gap is that "ICONIC Reserve" and "machine endpoints" are unexplained, so an agent without external context cannot tell what these endpoints are for.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. It correctly implies a no-argument call by not mentioning any inputs.

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 ("Discover") tied to concrete resources: status, machine endpoints, and capabilities of ICONIC Reserve. This distinguishes it from domain-action siblings like reserve_quote or reserve_plans, though it never names or contrasts them explicitly, leaving the agent to infer that this is the introspection entry point.

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?

"Discover" implies this is a first-call, exploratory tool, so usage is inferable rather than stated. There is no explicit when-to-use or when-not-to-use guidance and no pointer to reserve_assess or the other siblings as follow-ups, which would have made the routing decision unambiguous.

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