Message of the Day

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

With no annotations provided, the description carries the burden of disclosing read-only behavior, which it does by explicitly stating 'GET'. It also clarifies that the result is plain text, though it does not describe edge cases like empty MOTD values or server unavailability.

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 a single front-loaded sentence with no filler. It includes exactly the useful information: action, resource, and endpoint.

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, read-only text retrieval tool, the description is fully sufficient. The HTTP method, endpoint, and expected content are all stated, and no output schema is needed because the return type is described as text.

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 has zero parameters and the schema is fully complete, so there is no parameter documentation burden. The description correctly implies that no inputs are needed.

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 ('Get') with a concrete resource ('server MOTD text') and identifies the exact HTTP endpoint, which makes the tool's function unmistakable. It is clearly distinct from the many list-type 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 purpose is self-evident: use it to retrieve the server's message-of-the-day text. It does not explicitly mention alternatives, but no sibling tool serves this exact role and the context is clear enough for correct selection.

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