list_data_sources

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

No annotations are provided, so the description carries the full burden. The word 'List' reasonably implies a read-only operation, and 'with their data components' indicates what is returned. However, it does not disclose output shape, size limits, pagination, or any additional behavioral context, leaving some burden unmet.

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 a single, focused sentence with no filler. It front-loads the action and resource, and every word contributes meaningful information about what the tool returns.

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?

For a no-parameter listing tool, the description largely suffices: it names the domain (MITRE ATT&CK), the object (data sources), and the included detail (data components). It falls short only by not distinguishing itself from a similarly named sibling, which is a meaningful gap in this large tool catalog.

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 tool has zero parameters, so there is no parameter ambiguity to resolve. The schema already fully covers the absence of arguments, and the description adds no contradictory parameter information. The zero-parameter baseline of 4 is appropriate.

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 a specific action ('List all') and resource ('MITRE ATT&CK data sources'), and even notes the output includes data components. However, it does not differentiate this tool from the closely named sibling 'get_data_sources', so an agent could reasonably be unsure which sibling to call.

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 such as 'get_data_sources' or 'list_by_data_source'. It implies a full list use case with 'all', but does not state exclusions, prerequisites, or situations where a sibling tool would be more appropriate.

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