Delimit License Status

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds 'read-only' and explicitly names the underlying call 'ai.license.get_license', plus a return shape with next_steps. This is useful context beyond the annotations, though no rate limits or error behaviors are mentioned.

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 well-organized with clear sections and front-loaded purpose. It is slightly repetitive in stating the read-only nature multiple times ('this is a read', 'read-only', 'this reads license state'), but overall every section adds meaningful guidance.

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?

For a simple zero-parameter read-only tool, the description is complete: it explains purpose, usage triggers, exclusions, sibling contrast, side effects, underlying call, and return fields. No important detail an agent would need to call it correctly is missing.

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 schema is fully covered at 100%. The description includes 'Args: None,' which confirms the empty schema and gives agents no reason to invent arguments. This meets the no-parameter baseline.

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 opens with a specific verb and object: "Report the current Delimit license tier, validity, and expiry." This clearly identifies the resource and the action. It further distinguishes itself from siblings by noting it reads license state while gated tools call require_premium internally.

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?

Provides explicit 'When to use' and 'When NOT to use' sections, including diagnostic scenarios like require_premium rejections. It names concrete sibling tools and clarifies it is not for installing or rotating licenses.

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