probe_token_capabilities

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

Without annotations, the description fully bears transparency. It states the tool probes and returns a report of accessible vs denied endpoints, clearly indicating a read-only, non-destructive operation. A slight improvement would be to explicitly note it is safe and idempotent.

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 three sentences, each serving a distinct purpose: what it does, when to use it, what it returns. No redundant or irrelevant text.

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 zero parameters and an existing output schema, the description fully covers the tool's purpose, usage context, and behavior. It is complete for a simple diagnostic tool.

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?

There are zero parameters and schema coverage is 100%, so the description naturally adds no parameter details. The baseline of 4 is appropriate as no additional meaning is needed beyond the schema.

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 it probes token capabilities and specifies the resource (Spot.io API endpoints). It distinguishes from sibling tools which target specific resources like clusters or instances.

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 explicitly advises 'Call this first to understand what tools will work with your token', providing clear guidance on when to use it. It does not include explicit when-not-to-use but the context implies it's a preliminary diagnostic step.

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