GetEnhancementImpl

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

The description includes a '[read-only]' hint, indicating no side effects, but provides no other behavioral details such as authentication needs, rate limits, or error handling for missing implementations. Given no annotations, this is minimal but adequate.

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 concise sentence that front-loads the read-only hint and clearly states the purpose. No unnecessary words.

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 simple retrieval tool, the description is minimally complete, but it does not explain the return format of the source code or any potential error conditions. Context is adequate but could be richer.

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?

Schema coverage is 100%, so the schema already describes both parameters. The description does not add additional meaning beyond repeating the parameter names. Baseline 3 applies.

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 the verb 'Retrieve', the resource 'source code of a specific enhancement implementation', and the required identifiers (name and enhancement spot). It distinguishes itself from siblings like GetEnhancementSpot.

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 does not explicitly state when to use this tool versus alternatives like GetEnhancementSpot or GetEnhancements. Usage is implied, but no guidance is provided on when to choose this tool over others.

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