read_morning

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the constraint that arbitrary URLs, tokens, headers, or writes are not allowed, which is useful context beyond annotations, but it still does not disclose what the read/preview actually does, what it returns, or its limitations. With annotations carrying the safety profile, this is a modest addition, not rich transparency.

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?

It is a single efficient sentence with no waste, but it is so terse that it omits essential information, so conciseness comes at the cost of under-specification rather than being a virtue.

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 tool with a generic operationId-driven input schema, nested objects, no output schema, and many siblings, the description is far too thin. An agent has no idea what a 'reviewed read/preview' entails, what operationId values are valid, or how this differs from the sibling read and preview tools.

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 description coverage is 0% for the three parameters (operationId, body, parameters), so the description must carry the burden, yet it never mentions any parameter, its format, or what operationId selects. The mention of 'URLs, tokens, headers' hints at operation shape but does not explain the parameters.

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 says 'Run a reviewed read/preview operation' which gestures at a read/preview capability, but it never states what resource is read or previewed or what 'morning' refers to. It is vague enough that an agent cannot distinguish this tool from siblings like get_document or preview_document_draft.

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?

No when-to-use, when-not-to-use, or alternative is mentioned. The only constraint given is a negative one ('No arbitrary URLs, tokens, headers or writes'), which does not tell the agent when this tool is the right choice over the many sibling read/preview tools.

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