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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that, disclosing nothing about what the response contains, whether the entity assignment can be absent, or pagination/error behavior.

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 single substantive sentence is duplicated verbatim, which is pure waste, and the operation ID is metadata rather than usable content. It is short, but it is under-specified framing rather than earned brevity.

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?

With no output schema, a nested free-form query parameter, and 0% schema description coverage, the description would need to carry a lot. It supplies nothing about the return payload or the parameters, leaving the agent dependent entirely on describe_operation.

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 0% for both parameters, including a required path parameter 'id' and an untyped free-form 'query' object. The description provides no explanation of what 'id' identifies (site id) or what query options are accepted, so it fails to compensate for the coverage gap.

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 only restates the raw HTTP path 'GET /api/sites/:id/entity-assignment' twice, plus an operation ID. It never says in natural language what an 'entity assignment' is or what is being retrieved, so an agent gets the resource but no meaningful statement of purpose beyond the title.

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 guidance on when to use this versus siblings such as get_sites_by_id_366f0f998a651e6373e5df12 or get_sites_by_siteId_contacts. The only pointer, that describe_operation provides native request schemas, tells the agent how to fetch a schema, not when to select this tool.

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