Get a NightMarquee prompt

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds meaningful context beyond that by explaining that Free prompts need no account while Unlimited prompts require one, and it points to the sign-in sibling for the needed prerequisite.

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 sentences carry the essential information with no filler. The main action and the account requirement are front-loaded, and the mention of nightmarquee_sign_in is directly actionable.

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 low-complexity tool with one required parameter, full schema coverage, an output schema, and safety annotations, the description is complete. An agent can determine what the tool does, whether authentication is needed, and how to proceed if it is.

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 description coverage is 100%, so the schema already documents all three parameters fully. The description does not add parameter-specific detail beyond the schema, but it does reinforce the purpose of the tool and the auth context for retrieving prompts.

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 verb and resource: it fetches the full build prompt for one NightMarquee design, tuned for a target tool. This clearly distinguishes it from the sibling search tool, which finds prompts rather than retrieving their full content.

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 gives clear context about account requirements and tells the agent to run nightmarquee_sign_in for Unlimited prompts. It does not explicitly state when to prefer this over search_prompts, but the purpose and the schema's slug source make the intended flow reasonably clear.

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