Get Integration Models

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

Annotations already declare readOnlyHint=true and idempotentHint=true, which covers the safety profile. The description adds the scope 'all' (implying no filtering) and clarifies the purpose of integration models, but does not disclose additional behavioral traits such as return format, pagination, or authentication requirements. With annotations providing the key safety context, this description does not go beyond them significantly.

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 concise and well-structured. The first sentence states the action immediately, and the subsequent two sentences add valuable domain context about what integration models are and why they matter. Every sentence contributes meaning without redundancy.

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, no-parameter, read-only tool with an output schema, the description is largely complete. It explains the domain and purpose of integration models, which helps the agent understand the returned data. The only minor gap is the lack of explicit differentiation from the sibling tool get_integrations, but that is more of a usage guideline issue than a completeness gap.

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 no parameters, so there are no parameter semantics to explain. Per the evaluation rule, 0 params earns a baseline of 4, and the description does not need to compensate for any missing parameter details.

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 opens with a specific verb and resource: 'Get all integration models from Itential Platform.' This clearly distinguishes it from sibling tools like get_integrations (which likely lists active integrations) and create_integration_model (a write operation).

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 by the action 'Get all integration models' but there is no explicit guidance on when to choose this tool over alternatives such as get_integrations. The description provides background about what integration models are but does not state exclusions or alternative tool recommendations, leaving the agent to infer the appropriate context.

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