license_status

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

The description discloses that it returns a purchase link if no license is active, which is a key behavioral trait beyond a simple check. No annotations exist, so the description carries the full burden, and it does so adequately, though it could mention read-only nature.

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 the key purpose front-loaded. It is efficient and contains no unnecessary 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 (no parameters, no output schema), the description provides sufficient context: what it returns and a special case. However, it could describe the output format or possible values for completeness.

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 no parameters, so schema coverage is 100%. The baseline score of 4 applies, and the description does not need to add parameter information. It correctly implies no input needed.

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 'check current license status, tier, and expiry', specifying the verb and resource. It distinguishes from siblings like 'set_license' which is for modifying licenses, and 'check_prompt' which is unrelated.

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?

While no explicit when/when-not guidance is given, the context implies this tool is for checking license status only. The sibling 'set_license' provides an alternative for setting licenses, but the description could be improved by stating not to use this for other actions.

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