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

No annotations are provided, so the description carries the full behavioral burden. It says the pack includes a complete prompt, usage guide, and edge-case handling, which hints at packaged content, but it does not explain the actual output, whether content is generated or retrieved, permissions, or any operational constraints.

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 brief, but the opening sentence is a generic tagline rather than a front-loaded purpose statement. The remaining sentences are efficient enough, though they spend space on promotional phrasing instead of actionable detail.

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 one optional parameter, no annotations, and no output schema, the description should explain what the tool actually returns and how to use it. Instead it offers marketing copy and package contents without clarifying the output or invocation behavior.

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 single optional `query` parameter has 100% schema description coverage, so the schema already explains its purpose. The description adds no additional meaning about how the query scopes the analysis, but with high schema coverage the baseline of 3 is appropriate.

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 mostly restates the tool name as a 'ugc roi model prompt pack' and adds vague marketing phrasing like 'Turn expertise into output' and 'produce professional results.' It does not state a specific action such as generating, evaluating, or modeling ROI, nor does it distinguish this tool from the many UGC- and ROI-related siblings.

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?

It names restaurant and brand teams as the target audience, but gives no guidance on when to choose this tool over siblings like ugc-campaign-builder, ugc-campaign-workbench, roi-analyze-tool, or fnb-roi-gate. There are no exclusions, prerequisites, or alternative-selection cues.

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