creative_patterns

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

With no annotations, the description carries full burden. It discloses community-driven, cumulative data but lacks details on freshness, authentication needs, or rate limits. It mentions 'every prompt scored contributes' but does not explain update frequency.

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 three sentences, first front-loads the main purpose. It is reasonably concise, though the third sentence ('Also returns...') slightly disrupts flow. No unnecessary verbiage.

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 an output schema exists, the description sufficiently explains what the tool returns (patterns and enhancement unlocks) and the community signal context. It covers the main purpose without needing to detail output format.

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 100%, and the description does not add meaning beyond the schema's parameter definitions. The description mentions 'grade' and 'model' but without elaboration, meeting the baseline.

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 clearly states the tool returns community intelligence on patterns that produce high-grade prompts for a given model, including enhancement unlocks. It distinguishes itself from sibling tools like 'enhance_prompt' (which actually enhances) and 'score_prompt' (which scores single prompts).

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 usage for discovering effective patterns, but lacks explicit guidance on when to use this tool versus alternatives like 'community_benchmark' or 'score_and_enhance'. No when-not or comparison is provided.

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