Get Applications

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

Annotations already provide readOnlyHint=true and idempotentHint=true, so the safe read-only nature is given. The description adds context that the list is platform-wide ('configured on the Itential Platform instance'), which is useful. However, it does not disclose other behavioral details such as pagination, ordering, or response structure beyond what output schema might 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, clear sentence that immediately states the action and scope. There is no wasted wording or redundant information, making it as concise and effective as possible.

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 simplicity (0 params, read-only, no nested objects) and the presence of an output schema, the description sufficiently covers the essential context. It clearly identifies the resource and scope, and the output schema handles return value 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?

With zero parameters, there are no parameter semantics to explain. The schema itself is complete and the description adds no additional parameter information, which is appropriate for a parameterless tool. Baseline for 0 params is 4.

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 uses a specific verb 'Get' with a clear resource 'all applications' and clarifies scope as 'configured on the Itential Platform instance.' This distinguishes it from sibling tools like get_adapters or get_services, which retrieve different resource types.

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 clearly indicates this is for retrieving the full application list for the platform instance, providing enough context for when to use it. It does not explicitly mention alternatives or when not to use it, but the scope is unambiguous among the sibling listing tools.

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