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

With no annotations, the description must carry the full behavioral disclosure burden, but it only loosely mentions what the user 'gets' and 'pays.' It does not clarify whether this is a read-only lookup, whether it returns a list or a single item, or whether there are any side effects, rate limits, or dependencies.

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 short and front-loaded, which is good, but it reads more like a marketing tagline than a functional tool description. The dashes and fragmented phrasing are concise but sacrifice clarity and completeness.

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 tool with no annotations, no output schema, and only a vague description, important context is missing: return format, pagination, error behavior, pricing implications, and when to choose the search variant over the get variant. The description is minimally adequate for a single-parameter tool but leaves significant gaps.

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 schema provides only a bare 'q' string with 0% description coverage, so the description must compensate. 'Free text or code' adds basic meaning to the q parameter, but it lacks examples, format hints, or clarification of what kinds of codes are accepted.

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 identifies the resource (License) and suggests a free-text/code query mode, but it never states an explicit action verb like 'search' and relies heavily on the tool name for meaning. The phrase 'what it is, what you get, what you pay' hints at output content but is vague about what the tool actually does.

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?

There is no explicit guidance on when to use license_search versus license_get or any other sibling tool. 'Free text or code' implies an unstructured query use case, but no comparative context or exclusion is provided.

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