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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds concrete behavioral context: execution is synchronous, task support is forbidden, and the returned JSON is internal state with specific instructions on how to present results to the user (use assistantSummary, avoid raw JSON, suggest next actions). This significantly enhances the agent's understanding of expected behavior.

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 front-loaded with the core purpose, then adds a data caveat, followed by execution and response-handling instructions. It is somewhat verbose but each sentence adds meaningful context, especially the user-interaction rules. It earns its place, though it could be tightened.

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 an output schema and clear annotations, the description covers the tool's safety profile and output presentation well. However, given 9 optional parameters and no parameter descriptions, the tool's filtering capabilities and exact behavior remain underspecified. It is adequate but not complete for complex use.

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 0% and the description does not explain any of the 9 parameters. While parameter names and types are visible in the schema, the description provides no additional meaning about how filters like limit, website, or competitorId affect results. The description must compensate for zero schema coverage but fails to do so.

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 action (list), resource (qualified display evidence from saved canonical LeanrIQ Competitor Intelligence V2), and explicitly clarifies that cross-channel inspiration is not mixed in, distinguishing it from sibling intelligence tools. This makes the tool's purpose unambiguous and well-differentiated.

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 implies this tool is for display evidence specifically and mentions it does not include cross-channel inspiration, giving a clear context for when to use it. However, it does not explicitly name alternative tools or provide direct when-not-to-use guidance, so it stops short of a 5.

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