hello_tool

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

The description provides no behavioral information beyond what's in the name. With no annotations provided, the description carries the full burden of disclosing behavioral traits but fails to mention anything about what the tool actually does, what it returns, or any operational characteristics. This leaves the agent completely in the dark about the tool's behavior.

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?

While technically concise with just two words, this is under-specification rather than effective conciseness. The description doesn't convey meaningful information, so its brevity is a deficiency rather than a strength. Every sentence should earn its place, and this description fails to provide any value.

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 a tool with one parameter and no annotations or output schema, the description is completely inadequate. It provides no information about what the tool does, what it returns, or how it behaves. Even for a simple tool, 'Hello tool' fails to establish basic context or functionality, leaving the agent unable to understand when or how to use it.

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 schema description coverage is 100%, with the single parameter 'name' clearly documented in the schema as 'The name of the person to greet.' The description adds no parameter information beyond what the schema provides, which is acceptable given the high schema coverage. The baseline score of 3 reflects adequate parameter documentation through the schema alone.

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 'Hello tool' is a tautology that merely restates the tool name without specifying what it does. It provides no verb or resource information, making the purpose completely unclear. This fails to meet even the basic requirement of stating what the tool does.

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 offers no guidance on when to use this tool, what context it's appropriate for, or any alternatives. With no siblings listed, differentiation isn't needed, but the description still provides zero usage context, leaving the agent with no information about when this tool should be invoked.

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