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 fully covered by structured data. The description adds no behavior beyond that: it says nothing about the fact that returning config schemas requires filters (a constraint buried only in the schema), nor about result size, pagination, or scoping by workspace.

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 with no wasted wording; the content nouns are compact and scannable. It is efficient but so terse that it omits constraints that would have earned the space.

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 read-only metadata lookup with rich annotations and a moderately documented four-parameter schema, the essentials are covered elsewhere. However, the description omits the notable conditional rule that includeConfig=true requires an id or name filter, which is the most likely source of a failed call.

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?

With 75% schema description coverage the schema already documents includeConfig's filter requirement and the comma-separated id/name filters, so the baseline is 3. The description contributes no parameter meaning at all, leaving workspace_id undocumented in both places and the naming/id filter distinction solely to the 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 names a specific verb and resource ('Get destination definition metadata') and enumerates the content returned ('configuration schemas and capabilities'). It does not differentiate itself from nearby siblings such as get_destination, get_source_definitions, or get_audience_destination_schema, so an agent must infer the distinction from the name alone.

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: a caller infers this tool is for inspecting destination-type metadata and capabilities, presumably before connecting a destination. There is no explicit statement of when to use it, when not to, or which sibling to prefer for connection-level versus definition-level data.

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