GetEnhancementSpot

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

The description includes '[read-only]' indicating a safe read operation, but no annotations are provided, so the description must cover more behavioral traits. It does not mention permissions, side effects, return format, or error conditions, leaving significant gaps.

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, front-loaded with '[read-only]' and the core action. Every word adds value, with no unnecessary text.

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?

The description is minimal given the lack of annotations and output schema. It does not explain what 'metadata' includes, what the 'list of implementations' looks like, or any constraints. More detail would be beneficial compared to siblings like GetEnhancementImpl.

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 covers the single parameter with a description ('Name of the enhancement spot'), and the tool description does not add new insight beyond that. With 100% schema coverage, baseline 3 is appropriate.

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 clearly states 'Retrieve metadata and list of implementations for a specific enhancement spot,' specifying the verb, resource, and target. It differentiates from siblings like GetEnhancementImpl and GetEnhancements by focusing on a single spot and its metadata and implementations.

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 guidance on when to use this tool versus alternatives such as GetEnhancementImpl or GetEnhancements. The description does not provide any when-to-use or when-not-to-use context.

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