Get Entity Attributes

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

No annotations are provided, so the description must carry the full behavioral burden. It does not disclose whether this is a read-only operation (though implied by 'Get'), performance characteristics, caching behavior, or what specific PowerPlatform API concepts (like logical vs physical names) apply.

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?

Extremely concise at six words with no redundant text. However, it may be overly terse given the lack of annotations and presence of similar sibling tools; additional context would improve utility without sacrificing clarity.

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 simple two-parameter read operation with an output schema provided, the description covers the minimum. However, given the lack of annotations and the confusing similarity to 'get-entity-attribute', the description is incomplete regarding disambiguation and behavioral expectations.

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%, with 'entityName' and 'environment' both well-described in the schema. The description adds minimal semantic value beyond the schema, only confirming the PowerPlatform domain context. Baseline 3 is appropriate since the schema does the heavy lifting.

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 ('Get') and resource ('attributes/fields of a PowerPlatform entity'). However, it fails to distinguish from the similar sibling tool 'get-entity-attribute' (singular), which could confuse the agent about whether this retrieves all attributes or requires a specific attribute identifier.

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 siblings like 'get-entity-attribute', 'get-entity-metadata', or 'get-entity-relationships'. No prerequisites, conditions, or alternatives are mentioned.

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