madeonsol_deployer_alerts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds value by specifying it's real-time with KOL enrichment, and that 'before' cursor is preferred for pagination at scale. No contradictions.

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?

Two concise sentences: first states purpose and enrichment, second lists filters and pagination. Every sentence is informative with no fluff. Front-loaded with main action.

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?

While the description covers core functionality, it lacks details on the output structure (e.g., which fields each alert contains, KOL enrichment specifics). Since no output schema is provided, the agent might need to infer response format. For a tool with real-time enrichment, more output context is beneficial.

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?

Input schema has 100% documented parameters. The description reinforces key filter meanings (noise gating) and highlights the tier access restriction, adding context beyond schema descriptions. It also explains pagination preference, which is not in schema.

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 it retrieves real-time deployer alerts with KOL buy enrichment, listing specific filters and pagination method. The sibling list includes many alert tools, but this one is uniquely focused on deployers with KOL enrichment, providing clear differentiation.

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 provides filter tips and recommends cursor pagination over offset, but does not explicitly state when to use this tool versus alternatives like coordination alerts or KOL feed. No when-not or direct sibling differentiation is given.

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