dynatrace_managed_discover_entities

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

The readOnlyHint annotation already signals a safe read operation. The description adds useful behavioral context by stating that results include entity properties, tags, management zones, and relationship counts, and it emphasizes the single-type constraint. No contradiction with annotations exists.

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 only two sentences, front-loads the core purpose, and immediately surfaces the critical entitySelector constraint. The result-content sentence adds valuable context without unnecessary fluff.

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 discovery tool with full schema documentation and a read-only annotation, the description covers the main behavior, the core constraint, and the shape of results. It does not describe pagination or return structure explicitly, but the schema's limit parameter and the listed result fields provide sufficient context.

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 input schema covers all parameters and already documents entitySelector, mzSelector, time range, sort, limit, and environment_alias. The description mostly restates the entitySelector single-type rule already present in the schema, adding little new semantic meaning for parameters.

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 states a clear action ('Discover entities') with a specific resource ('Managed cluster') and method (EntitySelector syntax). It is distinguishable from sibling tools like get_entity_details because it implies a broader discovery/list operation, though it does not explicitly name any sibling.

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 gives a clear usage context: use it to discover entities via EntitySelector, and it highlights a critical prerequisite: exactly one entity type. However, it does not state when to prefer it over alternatives such as get_entity_details or get_entity_relationships, nor any when-not-to-use guidance.

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