crm_query_data

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

The annotations already reveal readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the description does not need to restate those. However, it adds nothing about side effects, return behavior, or whether the dispatched action can mutate CRM data.

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 compact and focused: two sentences plus concise per-parameter notes. There is no redundant or filler content.

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 an output schema exists, the description still fails to mention what the action returns. It also omits prerequisites, expected message format, and what kind of CRM queries are supported, leaving the agent without enough context to invoke it confidently.

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 schema has no parameter descriptions, so the two one-line descriptions are helpful but minimal. 'message' is described as a free-text objective and 'inputs' as an optional JSON string, but the expected JSON structure and how the two parameters interact are left unspecified.

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 action ('crm domain agent action query_data') and says it routes through a dispatcher, but it never explains what query_data actually does or what kind of CRM data it targets. It does not distinguish this from the many sibling CRM list/get tools.

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 given for when to use this tool instead of list_crm_tasks, list_crm_contacts, list_crm_deals, or dispatch_domain_agent. It does not describe the intended free-text vs structured-input workflow or provide examples.

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