review_licensing

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds only the vague intent 'preserve restrictive source boundaries' and does not explain outputs, what a triage verdict looks like, or how restrictive sources are handled, so it adds modest value beyond the annotations.

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?

It is a single front-loaded sentence with no filler, which is efficient. The terse, jargon-heavy phrasing ('restrictive source boundaries') costs a little clarity, but there is no wasted text.

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 a complex nested input schema and no output schema, the one-sentence description is too thin: it explains neither the required 'use'/'items' contract nor what the review returns. The agent would need the schema alone to call this correctly.

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 'items' parameter is a nested array of objects with many fields (license, evidence, noticeIncluded, provenancePreserved, redistributionPermission, etc.). The description only loosely gestures at the 'use' enum via 'end-project versus library redistribution' and does nothing to explain the per-item fields, leaving the agent without parameter meaning.

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 states a specific verb ('triage') and resource ('per-asset evidence') and ties it to the schema's 'end-project versus library redistribution' distinction, so the agent can tell this is a licensing review over assets. It does not explicitly differentiate itself from nearby siblings like check_media_provenance or verify_template_source, keeping it below a 5.

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 statement of when to use this tool versus alternatives such as check_media_provenance or verify_template_source. The phrase 'end-project versus library redistribution' hints at the use case but does not give conditions, prerequisites, or exclusions.

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