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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is known. The description adds nothing beyond that - no mention of what the mapping represents, whether it is paginated, or what the response contains, despite being an integration-configuration read.

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 same path sentence is repeated verbatim, which is pure waste, and the operation-ID boilerplate occupies a third of the text. It is short but badly structured, with no front-loaded explanation of purpose.

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 0% parameter documentation, no output schema, and a nested free-form query object, the description should carry substantial weight. Instead it supplies only a path, leaving the agent unable to tell what data comes back or how to scope the request.

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 two parameters (query and params.id), and the description only echoes ':id' from the path. It never explains that id is a connection identifier or what the free-form query object accepts, so it fails to compensate for the completely undocumented schema.

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 merely restates the HTTP verb and path from the title, with no explanation of what a 'dimension-slot-mapping' resource is or what the endpoint retrieves. An agent learns nothing it did not already get from the name/title combination.

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 call this versus the many sibling connection endpoints, or what the prerequisite state is. The only actionable hint is that describe_operation exposes native request schemas, which is a tooling note rather than usage guidance.

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