data_discover_data

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

Annotations mark destructiveHint true and readOnly false, but the description never discloses potential side effects. The tool name 'discover' may imply read-only behavior, making the lack of a warning especially concerning.

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 text is short and not padded, but most of it is boilerplate routing language that likely repeats across many sibling tools. It could be tighter if it replaced generic phrases with actual tool-specific semantics.

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?

No output format, return type, error behavior, or side-effect context is mentioned. With two opaque parameters and a destructive annotation, an agent cannot confidently predict what will happen when invoking this tool.

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 parameters message and inputs receive only generic one-line definitions ('free-text objective', 'optional JSON string') with no expected structure or examples. Since the schema itself has no descriptions, the added value is minimal.

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 only says to run a generic 'data domain agent action' named discover_data, with no explanation of what discovery does or what data it affects. It is indistinguishable from many other domain-agent dispatch tools beyond the name.

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 use this tool over any sibling domain/agent/data tool. Message and inputs are described only as free-text and JSON, with no examples, conditions, or success criteria.

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