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

Annotations declare readOnlyHint=true, but the description adds real value beyond that: it discloses that the path is validated server-side to allow only .get/.list/.check/.preview_* actions and that write actions are rejected. That enforcement mechanism is genuine behavioral context an agent could not infer from the annotation alone.

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, front-loaded with the escape-hatch framing followed by the safety constraint and the API shape. Every sentence carries information and nothing is padded.

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?

There is no output schema, and since this is a generic passthrough the return shape is inherently arbitrary, so the description reasonably focuses on what's controllable: the path constraint and read-only guarantee. It could note that responses mirror the underlying Autumn endpoint, but the essentials for correct invocation are present.

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%, so both the path (with example format and suffix constraint) and the body object are already documented in the schema. The description restates the POST {path} pattern and the allowed suffixes, adding little beyond the structured fields, so the baseline 3 applies.

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 gives a specific verb+resource: POST to any Autumn read/preview endpoint, framed as a power-user escape hatch. It distinguishes itself from siblings by scoping to endpoints 'not wrapped by a dedicated tool', which is exactly the differentiator against the 17 dedicated tools listed.

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 clearly conveys the usage condition (only when no dedicated tool covers the endpoint) and enforces the read-only boundary. However, it never explicitly names an alternative or states a 'prefer the dedicated tool' directive in when/when-not form, so the routing guidance is implied rather than spelled out.

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