decode_entity_guid

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

With no annotations, the description carries the disclosure burden. It reveals the operation is purely local ('without making an API call') and specifies what the output contains. It does not mention invalid-GUID error behavior, but that is a minor gap for a simple decode operation.

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?

Two efficient sentences, front-loaded with the operation and output components, and the use-case sentence adds value with no redundancy.

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 one-parameter utility with no output schema, the description fully covers what the tool does, what it returns, and why to use it. Nothing critical is missing for invocation or result interpretation.

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 already documents the single guid parameter, so baseline is 3. The description adds meaningful context by noting the GUID is base64-encoded and what components are revealed, helping the agent form valid input and interpret the output.

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 ('Decode') and resource ('New Relic entity GUID'), and explicitly lists the revealed components (account ID, domain, entity type, domain ID), making the purpose unmistakable. This distinguishes it clearly from sibling tools like get_entity or entity_search.

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 provides clear usage context: useful for understanding what an entity GUID refers to without making an API call. This implies when to use it instead of fetching full entity data, though it does not explicitly name alternatives or state exclusions.

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