say_hello

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

No annotations are provided, so the description carries full burden. It only states the action without disclosing side effects, return value, authentication needs, or any other behavioral traits. For a 'hello' tool, the behavior might be obvious, but it fails to state what happens or what is returned.

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, focused sentence with no wasted words. It is appropriately concise for the tool's simplicity and does not repeat schema information.

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 very low complexity (one parameter, no output schema), the description covers the core action but omits return value and any side effects. It is minimally complete for a simple tool, but could still benefit from a brief mention of what the tool returns.

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 has one parameter 'name' with 0% description coverage. The description does not explicitly explain that 'name' refers to the person being greeted, though it is loosely implied. The tool fails to compensate for the lack of schema descriptions.

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 'Say hello to a person' uses a specific verb ('say') and resource ('person'), clearly distinguishing this from all sibling GCP management tools. It fully communicates the tool's purpose with no ambiguity.

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 usage context is implied—'say hello' naturally indicates when to invoke this tool. However, there is no explicit guidance on when not to use it or mention of alternatives, but given the trivial nature and clear purpose, the implied usage is sufficient.

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