graylog_list_profiles

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

The description is straightforward for a list operation, and 'List' implies a read-only behavior. However, no annotations are provided, and the description does not explicitly disclose that no data is mutated, nor does it mention any permissions, pagination, or error behavior. It adds some context with 'trigger aliases' but stops short of a fuller behavioral disclosure.

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, clear sentence with no filler. It front-loads the core action ('List') and resource, and every word contributes to understanding the tool's function.

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 operation with zero parameters and an output schema present, the description covers the essential purpose and output contents ('profiles and their trigger aliases'). It does not mention potential caveats like result limits or ordering, but given the simplicity of the tool, this is sufficient.

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, and the schema is empty. According to the rubric, a baseline of 4 applies when there are no parameters. The description does not need to compensate for any parameter ambiguity since there are none.

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 a specific action ('List') on a specific resource ('business diagnosis profiles') and adds the detail of 'trigger aliases' in the output. This clearly distinguishes it from sibling tools like graylog_get_profile, which targets a single profile.

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?

Usage is implied: use this tool when you need to enumerate all available business diagnosis profiles. However, there is no explicit mention of when NOT to use it or alternatives, such as graylog_get_profile for a specific profile. The sibling tool names provide context but the description itself offers no direct guidance.

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