Get Entity Relationships

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

No annotations provided, so description carries full disclosure burden. Adds specificity by enumerating relationship types (1:N, N:N) not obvious from the tool name, but omits safety characteristics (read-only), performance implications, or side effects.

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?

Single sentence efficiently front-loaded with the action verb. No wasted words, though brevity may be excessive given zero annotation coverage and the need for behavioral context.

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?

Adequate for a simple read operation with 100% schema coverage and existing output schema (relieving need to document return values). However, lacks behavioral context that annotations would normally provide, leaving gaps in safety and operational characteristics.

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%, establishing baseline 3. Description implies the entityName refers to a PowerPlatform logical name, but adds no syntax examples, format constraints, or semantic details beyond what the schema already provides.

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 specific action ('Get') and resource ('relationships'), distinguishing from sibling tools like get-entity-attributes by specifying relationship types ('one-to-many and many-to-many'). Clarifies this targets PowerPlatform entities.

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?

Provides no guidance on when to use this tool versus alternatives like get-entity-metadata (which might overlap) or prerequisites for invocation. No mention of when the optional environment parameter should be specified.

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