data_describe_source

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

The annotations declare destructiveHint=true, but the description suggests a read-only operation ('describe_source') and provides no warning or clarification about destructive effects. This omission is misleading and contradicts the annotation's intent, especially given the tool's name implies harmless inspection.

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 description is short and front-loaded with the action name and routing context. It avoids unnecessary fluff, but the brevity comes at the cost of purpose clarity, so it is not a perfect conciseness score.

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?

Given the tool's complexity (many siblings, output schema present, but no output description), the description omits crucial details: what 'describe_source' returns, when it is appropriate, and any side effects. An agent cannot decide to use it confidently based on this text alone.

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?

The description explains each parameter: 'message' is a free-text objective and 'inputs' is an optional JSON string. This adds meaning beyond the bare schema (which only provides titles and defaults), giving agents a better understanding of what to provide.

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 says 'Run the data domain agent action `describe_source`' but does not explain what 'describe_source' does or what a 'source' refers to. It lacks a clear verb-resource mapping beyond the name itself, leaving ambiguity about the tool's actual purpose.

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?

No guidance is provided on when to use this tool versus its many siblings (e.g., other 'describe' or domain-agent tools). There are no explicit conditions, exclusions, or alternative recommendations.

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