engain_list_opportunities

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

Lacks disclosure of key behaviors like pagination (cursor parameter), sorting behavior, return format, or whether it is read-only. No annotations are provided, so the description carries full burden but fails to address these traits.

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?

Extremely concise: two sentences with no fluff. Main purpose and type selection are front-loaded. Every word adds 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?

Given 5 parameters, no output schema, and no annotations, the description is too brief. It omits important context like pagination, sorting details, error conditions, and project ID defaulting (partially in schema).

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?

Only the 'type' parameter gets partial explanation (selects new Reddit or SEO opportunities). With schema coverage at 20%, the description does not compensate for the undocumented parameters (cursor, sortBy, numItems, projectId default behavior).

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?

Description clearly states the tool lists opportunities for a project and distinguishes by type (new Reddit vs SEO). This verb+resource combination is specific and differentiates from siblings like engain_get_opportunity which retrieves a single opportunity.

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?

No explicit guidance on when to use this tool vs alternatives such as engain_get_opportunity for a single opportunity or other list tools. The description does not state when not to use it.

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