rhsm__get_activation_keys

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

Annotations already declare readOnlyHint=true, so the description adds value with the 'CALL IMMEDIATELY' behavioral cue. It explains the purpose of activation keys for RHEL registration, which supplements the annotation without contradiction.

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 relatively concise with a clear opening, a call-to-action flag, and a brief explanation. It could be slightly more concise, but overall well-structured and front-loaded.

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 low complexity, full schema coverage, presence of annotations, and existence of an output schema, the description provides all necessary context: what the tool does, when to call, and what it returns (list of activation keys with details).

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 input schema has 100% description coverage for both parameters (limit, offset) with defaults and descriptions. The description does not add any additional parameter semantics beyond what is already in the schema, so baseline score applies.

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 'Get the list of activation keys available to the authenticated user,' which clearly specifies the action (get) and resource (activation keys). It distinguishes from sibling tools like 'rhsm__get_activation_key' (singular) by indicating it returns a list.

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?

Includes a 'CALL IMMEDIATELY - No information gathering required' flag, guiding the agent to invoke without prior steps. However, it does not explicitly mention alternative tools for getting a single key or when not to use this tool.

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