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

Annotations already state readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds only 'Returns only data visible to the linked Market Brew account,' which is a minor scoping note. It does not disclose return format, pagination, or error behavior. Given annotations carry the load, this is barely adequate.

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?

Two short sentences with no waste, but the first sentence is a tautology and the second is marginally useful. Front-loading is fine, but content is low-value.

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?

With no output schema, 0% schema coverage, and two required parameters, the description should explain what the tool returns and what the parameters mean. It does neither, leaving the agent with insufficient guidance to invoke correctly beyond the obvious.

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%, and the description mentions no parameters. Both 'crew' and 'licenseId' are required but undocumented in both schema and description. For a tool with 2 required parameters, this is a significant failure to compensate.

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 essentially restates the tool name ('get a customer license') without adding a specific verb+resource differentiation. The sibling 'list_customer_licenses' exists, but the description doesn't clarify how this differs from listing licenses. It's tautological.

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 says 'Use this when the user asks to get a customer license,' which is circular and provides no when-to-use vs. alternatives guidance. No mention of get_license_definition or list_customer_licenses as related tools.

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