get_administrations

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

With no annotations, the description carries the full burden. It discloses the operation type ('List'), the authorization context ('accessible with the configured API key'), and the primary purpose (discovering administrationID). It does not mention return format or error cases, but for a simple listing operation with no parameters, this is sufficient transparency.

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?

Two concise sentences that front-load the verb and resource, then add a critical usage hint. No filler words or redundant details. Every sentence earns its place.

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, no output schema), the description covers what the tool does, what it returns (list of administrations), how it's authenticated, and how to use it. It is fully complete for its context.

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 tool has zero parameters, so the baseline for this dimension is 4. The description adds value by explaining the purpose of the tool's output rather than needing to clarify parameter syntax. No parameter information is missing.

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 ('List') and identifies the exact resource ('Yuki administrations (companies)'). It clarifies the scope ('accessible with the configured API key') and distinguishes this from the sibling tool 'get_administration_id' by implying that this returns all administrations rather than a specific one.

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?

Explicitly instructs 'Run this first to discover the correct administrationID to pass to other tools,' giving clear when-to-use guidance and explaining how the output is consumed by other tools. This is strong contextual usage direction.

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