Get Entity Attribute

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

No annotations are provided, so the description carries full burden. It fails to disclose that this retrieves schema/metadata about an attribute (not actual field values from records), does not describe the return format despite the existence of an output schema, and omits any mention of permissions or error states.

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, efficient sentence that front-loads the action. However, given the lack of annotations and ambiguity around the tool's behavior, the extreme brevity leaves critical gaps rather than earning efficiency points.

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?

Despite having an output schema to handle return value documentation, the description is incomplete for agent selection. It lacks critical context to distinguish this metadata retrieval tool from data retrieval siblings (get-record, query-records) and does not explain the PowerPlatform 'attribute' concept for users unfamiliar with the platform.

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 clear descriptions for entityName, attributeName, and environment. The description adds no additional semantic information beyond the schema, which is acceptable given the high coverage baseline.

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 the verb (Get) and resource (specific attribute/field of a PowerPlatform entity). It implicitly distinguishes from sibling 'get-entity-attributes' (plural) by emphasizing 'specific,' though it does not explicitly name the sibling tool or clarify whether this retrieves schema metadata vs. record data.

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?

No guidance provided on when to use this tool versus alternatives like 'get-entity-attributes', 'get-entity-metadata', or 'get-record'. No prerequisites or conditions are mentioned.

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