get_entity

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine context beyond that: the golden metrics are the actual NRQL New Relic uses for that entity type and can be run as-is via run_nrql. That is useful, but it leaves gaps such as error/not-found behavior for an unknown guid.

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 short sentences, front-loaded with the action and return contents. The second sentence earns its place by explaining what the golden metrics are and how to use them. Minor room to tighten but 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?

An output schema exists, so return values need not be restated, and annotations carry the read-only safety profile. For a single-parameter lookup the description covers the essentials, with the only real omission being explicit routing versus search_entities.

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% and the single guid parameter is already documented as 'Entity GUID returned by search_entities'. The description adds no format, syntax, or sourcing detail beyond what the schema states, so the 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?

States a specific verb and resource ('Get one entity') and enumerates what comes back (tags, golden metrics, relationships). It does not explicitly contrast itself with the sibling search_entities, so an agent must infer the difference from 'one' vs. 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?

Usage is only implied: 'Get one entity' suggests retrieving a single known entity, presumably after search_entities, but the description never states when to use this rather than alternatives or what prerequisites exist. The run_nrql mention is a pointer to a related tool, not guidance on selecting this one.

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