Get item

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered externally. The description contributes the exact-match/case-sensitivity framing but says nothing about not-found behavior or whether missing items return empty vs. error.

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?

A single front-loaded sentence with no filler; the key constraint (exact code) is placed where it is read first.

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 two-parameter, fully documented read tool with rich annotations and no output schema, this is close to sufficient. The only meaningful omission is behavior on a non-existent ItemCode and whether 'fields' projection affects payload size.

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 description coverage is 100%, including the case-sensitivity note on HANA and the full enum list for 'fields'. The description's mention of 'exact ItemCode' restates the schema rather than adding format, casing, or projection guidance.

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?

Names a specific verb (Fetch) and resource (one item master record) with the lookup key (exact ItemCode), so an agent knows this is a single-record exact-match read. It does not explicitly name search_items as the alternative for fuzzy/list lookups, so the sibling distinction is only implied by 'one' and 'exact'.

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 phrase 'by its exact ItemCode' implies the precondition for use (you must already know the code), which is meaningful guidance. But it never states when to prefer search_items instead, nor what happens when the code does not exist.

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