Get item

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds the behavioral detail that the id parameter can be either a FastBound GUID or an externalId, which goes beyond the schema. However, it does not disclose error handling or not-found behavior, so it only partially adds context.

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 of 17 words, front-loaded with the main action and resource. There is no redundant or extraneous 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 low complexity (2 parameters, 1 required), complete schema documentation, and readOnlyHint annotation, the description sufficiently covers the tool's purpose and usage. No output schema is needed for a simple get-by-id tool, and the description states exactly what is retrieved.

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%, with both parameters clearly documented. The description summarizes the purpose of the id and idType parameters ('by FastBound GUID id or by your externalId'), but adds no further semantics like value formats or constraints beyond what the schema already provides.

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 uses a specific verb 'Retrieve' and identifies the resource as 'a single firearm record', with explicit lookup methods ('by FastBound GUID id or by your externalId'). It clearly distinguishes this from sibling search tools like search_items, which are for broader queries.

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 implies this tool should be used when a single known identifier (either FastBound GUID or externalId) needs to be fetched. It does not explicitly name alternatives, but the context of sibling tools like search_items suggests a clear usage boundary.

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