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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the useful fact that the response bundles configuration, sources and transformations - relevant since there is no output schema - but says nothing about permissions, rate limits, or how deeply those sub-objects are returned.

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?

A single front-loaded sentence that identifies the resource and immediately enumerates the payload contents. Zero filler.

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 tool with full annotations, the description covers purpose and return contents adequately. It leaves gaps on the undocumented workspace_id and on how to choose this over the many sibling destination tools.

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 only 50%, and the one documented parameter (destination_id, sourced from list_destinations output) is documented in the schema itself, not the description. workspace_id has no description anywhere, and the tool description adds no meaning about either parameter.

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 gives a specific verb and resource ('Get complete destination details') and enumerates what is included: configuration, connected sources and transformations. That distinguishes it from list_destinations or get_destination_definitions by content, though it never names a sibling explicitly.

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?

Usage is only implied: 'complete details' suggests fetching a single destination after listing, and the destination_id description points back to list_destinations. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. get_destination_event_metrics for metrics).

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