greet

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

Annotations indicate readOnlyHint=true and openWorldHint=true, which already tell the agent this is a safe read operation with open-world assumptions. The description adds minimal behavioral context by mentioning 'middleware functionality,' but doesn't disclose any additional traits like rate limits, authentication needs, or what 'greeting' actually returns. No contradiction with annotations exists.

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 sentence that's appropriately sized and front-loaded, stating the tool's purpose efficiently. There's no wasted text, though it could be more informative. It earns its place by at least indicating the tool's role.

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?

Given the tool's simplicity (1 optional parameter, no output schema), the description is incomplete. It doesn't explain what the greeting does, what it returns, or how it interacts with the middleware. Annotations cover safety, but the description lacks enough detail for an agent to understand the tool's full behavior in context.

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 input schema has 1 parameter with 0% description coverage, but the description doesn't mention parameters at all. Since there's only 1 optional parameter, the baseline is 4. The description doesn't add meaning beyond the schema, but the low parameter count makes this less critical.

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 states the tool 'greets' and mentions it demonstrates middleware functionality, which provides a vague purpose. It doesn't specify what resource is being acted upon or how it differs from sibling tools, which are all currency-related. The description is not tautological but lacks specificity about what 'greeting' entails.

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 description provides no guidance on when to use this tool versus alternatives. It mentions middleware functionality, but this doesn't help an agent decide between this greeting tool and the sibling currency conversion tools. There are no explicit when/when-not statements or named alternatives.

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