get_contract

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Get... information', implying a read operation, but does not confirm non-destructiveness, authentication needs, or any rate limits. The lack of explicit safety information is a gap.

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 short sentence, efficiently conveying the core purpose. It does not waste words, though it could optionally add structure like 'No parameters required.' It is well 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 absence of an output schema, the description should provide more context about what 'contract and resource limit information' includes. The agent may need to know the response structure, especially since there are no parameters. The current description is too minimal for complete understanding.

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 parameter semantics are trivial. The description prefaces 'contract and resource limit information', which hints at the expected output but does not need to explain parameters. Schema coverage is 100%, and baseline for zero parameters 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 clearly states 'Get contract and resource limit information for your IONOS CLOUD account', specifying the verb 'Get' and the resource 'contract and resource limit info'. Among siblings, which are specific resource getters (get_datacenter, get_server, etc.), this tool is uniquely for account-level contract details, providing clear differentiation.

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 provides no guidance on when to use this tool versus alternatives (e.g., list_activitylog_contracts for activity logs). There are no usage context or exclusion notes, leaving the agent to infer solely from the name.

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