entity_search

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

No annotations are provided, so the description carries the full burden. It discloses partial matching on name, filtering capabilities, and the effect of minimal_output. It does not mention pagination or sorting, but overall adequately explains the tool's behavior.

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 paragraph with every sentence adding value. It front-loads the main action and then provides specifics, achieving conciseness without omitting essential details.

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?

With 6 parameters and no required params, the description covers key aspects: search criteria, output fields, filtering options, and response size control. It lacks details on error handling or exact output structure, but given no output schema, it is sufficiently complete.

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 description adds meaningful context beyond the schema, such as lists of valid domain and type values, defaults and max for limit, and the effect of minimal_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 clearly states it searches for New Relic entities by name, type, domain, or tags, and lists returned data (GUIDs, alert severity, metadata). It distinguishes itself from siblings like get_entity and get_entity_tags which are more specific.

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 explicit domain and type values, explains minimal_output and limit parameters, and how to reduce response size. It lacks explicit when-not-to-use or alternatives, but the context of sibling tools implies specific use cases.

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