get_entity

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

No annotations are provided, so the description carries the burden of explaining behavior. It clearly communicates that this is a read-style lookup returning full entity details, including concrete examples of type-specific metadata. It does not explicitly state 'read-only' or mention error behavior, but the lookup framing and return-value focus make the tool's behavior reasonably transparent.

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 three sentences and every sentence earns its place: the first states the core action, the second details expected returns, and the third routes to sibling tools. It is front-loaded with the most important information and contains no filler.

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?

This is a simple single-parameter read tool with no output schema, and the description covers all essential context: what the tool does, what the input is, what will be returned, and which sibling tools to use instead for related needs. Nothing critical for a correct invocation or selection is missing.

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, but the description adds useful context by identifying it as the New Relic entity GUID and pointing to entity_search as the way to discover GUIDs. This helps an agent understand where the value comes from and what format to supply, going slightly beyond the bare schema.

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 opens with a specific verb and resource: 'Look up a single New Relic entity by its GUID.' It lists the exact kinds of details returned, such as name, type, alert severity, tags, and type-specific metadata, which clearly distinguishes this tool from siblings like entity_search and decode_entity_guid.

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 explicitly states when to use alternatives: 'Use entity_search to find GUIDs, or decode_entity_guid to inspect a GUID without an API call.' This tells an agent which tool to choose based on the current need and implies that get_entity is for when you already have a GUID and want full entity details.

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