engineering_sensor_anomaly_detection

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

The description mentions routing through the platform's domain-agent dispatcher and scoping under JWT, tenant, and company, which provides minimal behavioral insight. However, it does not disclose whether the action is read-only, destructive, or any side effects, rate limits, or additional behaviors. With no annotations, the description carries the full burden and falls short.

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 concise: one sentence for the action, one for routing, then an args list. It is front-loaded with the core verb and resource. However, the concise nature comes at the cost of missing essential details, but it is well-structured.

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 name suggests sensor anomaly detection, the description fails to explain what anomaly detection does, what results to expect, or any prerequisites. Although it has an output schema (so return values are covered), the description lacks the core functional context needed for an agent to properly invoke it.

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 0%. The description adds minimal value: 'message: Free-text objective for the action' and 'inputs: Optional JSON string of structured inputs for the action.' While it identifies the parameters, it does not explain valid values, required formats, or how they affect execution.

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 states 'Run the engineering domain agent action sensor_anomaly_detection.' This is essentially a restatement of the tool name, providing no explanation of what anomaly detection entails. It does not clarify the specific resource or verb, nor does it differentiate from sibling tools like engineering_chat or engineering_compare_model_versions.

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?

The description gives no guidance on when to use this tool versus alternatives. It lacks any context about typical scenarios, prerequisites, or exclusions. Among many sibling engineering tools, there is no direction on when to choose this one.

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