malcolm_data_coverage

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

The description discloses expected outputs (sensor timestamps, data age, document counts, index sizes) without annotations. It implies a read-only operation but does not detail side effects or performance implications.

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 moderately concise, with a clear front-loaded purpose and bulleted highlights. The args list is brief but could be more integrated.

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 purpose and presence of an output schema, the description provides a good overview of what to expect. It covers key aspects but omits details on return format and parameter effects.

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 parameter descriptions are minimal, only mentioning 'dateparser format' for time_from and lacking explanation of defaults or exact behavior. With 0% schema coverage, the description fails to compensate adequately.

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 clearly states it shows data freshness, sensor status, and dataset distribution, listing specific reports. It differentiates from sibling tools by focusing on pre-hunt coverage assessment.

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 explicitly advises calling the tool 'before a hunt to understand what data is available,' providing clear usage context. It does not explicitly exclude alternatives or mention when not to use, but the guidance is sufficient.

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