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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered and the bar for credit is lower. The description adds nothing beyond them: it does not mention that includeConfig=true imposes a mandatory filter dependency, nor anything about response volume, pagination, or what "capabilities" actually contains.

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 filler or redundancy. It is efficient, though the brevity borders on under-specification rather than tightness.

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, the description carries the burden of explaining what is returned, yet "configuration schemas and capabilities" is too abstract to tell an agent what fields or objects come back. For a two-required-parameter read tool with a conditional dependency, it leaves meaningful gaps about both selection and results.

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 75%, with the conditional includeConfig constraint and both filter parameters already documented in the schema. The description contributes no additional meaning about the required workspace_id scope or how the id/name filters behave, so the schema is doing essentially all the work.

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 source definition metadata") and adds scope in "configuration schemas and capabilities." However, it does nothing to distinguish this from siblings such as get_source, list_sources, or the analogous get_destination_definitions, so an agent cannot tell which catalog-vs-instance tool to pick from the text 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?

There is no when-to-use guidance, no exclusions, and no reference to any alternative tool. The agent is left to infer from the name whether this returns a catalog of source types or definitions of already-configured sources in the workspace.

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