Labs64/NetLicensing-MCP

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

No annotations are provided, so the description carries full burden. It implies a destructive action ('Revoke') but doesn't clarify if it's permanent, requires specific permissions, has side effects (e.g., invalidating associated sessions), or rate limits. The description lacks behavioral details beyond the basic action, leaving gaps for safe agent operation.

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 brief and front-loaded with the main action. The two-sentence structure is efficient, though the 'Args:' section could be integrated more smoothly. No extraneous information is included, making it easy to parse quickly.

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 a destructive tool with no annotations, 1 parameter, and an output schema (which handles return values), the description is minimally adequate. It states the action and parameter but lacks critical context like safety warnings, permissions, or error handling. The presence of an output schema lifts some burden, but more behavioral detail would improve completeness for a mutation 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?

Schema description coverage is 0%, but the description adds minimal param info: 'token_number: Token to revoke'. This clarifies the parameter's role but doesn't provide format, examples, or constraints. With 1 parameter and low schema coverage, it partially compensates but remains basic. Baseline 3 is appropriate as it adds some meaning beyond the bare 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 the action ('Revoke') and target ('API or shop token'), making the purpose evident. It distinguishes from siblings like 'netlicensing_get_token' (read) and 'netlicensing_create_api_token'/'netlicensing_create_shop_token' (create). However, it doesn't specify the resource type beyond 'token' or differentiate from other delete operations like 'netlicensing_delete_bundle'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., token existence), consequences (e.g., irreversible deletion), or when to choose this over other token-related tools like 'netlicensing_get_token' for checking status. The description only states what it does, not when to apply it.

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