get_contract

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

The annotation readOnlyHint=true already signals a safe read operation. The description adds no extra behavioral context beyond restating the purpose. It does not disclose what resource limits are included, any authentication requirements, or other effects. Since annotations carry the burden, a score of 3 is appropriate.

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 sentence with no filler or repetition. It conveys the essential information efficiently, adhering to strong conciseness.

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 one-parameter read-only tool, the description is adequate but leaves ambiguity about what 'resource limit information' entails. Without an output schema, the agent might not know the exact structure. Given low complexity, it's reasonably complete but not outstanding.

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 schema fully describes the only parameter 'depth' with a clear description, so schema coverage is 100%. The description adds no additional meaning about parameters, which is acceptable given the schema's clarity. Baseline 3 is justified.

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 the verb 'Get' and the resource 'contract and resource limit information' for an IONOS cloud account. This is specific and distinguishes it from sibling tools like 'list_activitylog_contracts' or other get_* tools for different resources.

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 indicates what the tool does but provides no guidance on when to use it versus alternatives. Since there is no direct sibling for fetching contract info, the implied usage is clear, but explicit context is lacking. No mention of when not to use it or which alternative to choose.

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