list-rum-applications

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

Annotations already contain readOnlyHint: true and openWorldHint: true, which indicate the tool is safe to use and returns all available items. The description adds no new behavioral context beyond confirming 'List all', so it does not exceed what annotations provide.

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, well-structured sentence that immediately conveys the tool's purpose. There is no unnecessary information.

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 simple list tool with no parameters and no output schema, the description is adequate. It states the action and scope. However, some details about what information is returned per application would improve completeness, especially since output schema is absent.

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 no parameters (empty input schema), so there is nothing to document. The description accurately reflects this by not mentioning parameters. Schema coverage is complete at 100%.

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 the verb 'List', the resource 'RUM applications', and the scope 'in your Datadog organization'. It distinguishes from sibling tools like create-rum-application, get-rum-application, and others that deal with different RUM entities.

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 is straightforward, indicating that this tool lists all RUM applications. It does not explicitly mention when to use this versus get-rum-application, but the purpose is clear enough that an agent would understand to use this for a complete list.

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