check_tier_status

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It does state that it shows which environment variables are set, which gives some transparency about its read-only nature. However, it does not mention whether it requires any specific setup, what the response format is, or any potential side effects, leaving gaps for the agent.

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 two sentences, concise and front-loaded. The first sentence states the primary purpose, and the second adds a relevant detail about environment variables. No wasted words.

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 parameters, no output schema), the description provides enough context: it explains what the tool checks and the nature of the output (environment variable status). However, it could be slightly more explicit about what 'configured and available' means or what the agent should do with this information, though the sibling tools suggest a clear 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 description is not required to explain parameter semantics. The baseline for 0 parameters is 4, and the description adds value by clarifying the tool's purpose rather than repeating schema information.

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 tool's function: checking which API tiers are configured and available. The verb 'Check' is specific, and the resource 'API tiers' is distinct from the sibling tools (OCR/PDF operations), making it easy to differentiate.

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 does not explicitly state when to use this tool versus alternatives, but the sibling tools are all OCR/PDF operations, so the usage context is implied: this is a configuration/diagnostic tool. No exclusions or alternative instructions are provided, so it earns a mid score.

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