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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description goes beyond them usefully: it discloses the returned fields (license type, verification status, terms_url), explains that 'Anonymous' names reflect a rights-holder privacy choice, and states that no account is required. It also warns that results are not authorization — a behavioral caveat not captured in any annotation.

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?

Front-loaded with purpose and usage before alternatives and caveats, and most sentences earn their place. The parameter enumeration sentence duplicates structured schema information and could be dropped, which keeps it short of fully economical.

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, the description correctly supplies the return shape and the terms_url follow-up path. For a simple four-parameter read-only search it covers purpose, when to use, auth requirements, semantic caveats, and the next step — nothing an agent needs to call it 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?

Schema coverage is 50% (search and license_type are documented in-schema), so the schema carries much of the load. The description's 'Optional: search (text), license_type, limit 1-100, offset' largely restates the schema and adds no meaning for offset or how limit/offset interact for pagination. Adequate, but it does not compensate for the undocumented pagination parameters.

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?

States a specific verb and resource — search publicly discoverable WEIR AI identity licenses — and scopes it to public listings only. It explicitly contrasts itself with siblings: get_public_license for a single entry and check_identity for one named person's clearance. An agent can route correctly without opening any schema.

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?

Gives an explicit when-to-use trigger (a user wants publicly listed likeness licensing options, e.g. for a campaign) plus named alternatives for adjacent intents. It also adds a guardrail that search results do not establish permission, which tells the agent what not to infer.

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