provider_resolve_entity

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

Annotations already state readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds nothing beyond the raw HTTP path: it doesn't say what a resolve returns, how it behaves for unknown/ambiguous IDs, or that it spans arbitrary domains (openWorld).

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?

It is short and front-loaded, but the second line merely restates the title/annotation (the same GET path), so it spends space without adding information.

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 an open-world generic entity resolver with no output schema, the description should explain what kind of object comes back and what 'entity' covers here. It leaves the agent unable to decide between this and the dozens of typed get-by-id siblings.

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 coverage is 100% and the single `id` parameter is documented as "the URN of the entity to be resolved (path)", so the schema does the work. The description adds no extra meaning about URN format or where such a URN comes from — baseline 3 applies.

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?

"Get specified entity object" gives a verb and a resource, but "entity" is undefined and generic in a server with dozens of get_* siblings. An agent cannot tell whether this fetches a user, a deployment, a network, or a catalog item, nor how it differs from the more specific get tools.

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?

There is no indication of when this generic resolver should be preferred over the many typed provider_get_* / iaas_get_* siblings. No prerequisites, no exclusions, no alternative named.

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