Post & Present

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

With no annotations, the description still makes clear that this is an informational/onboarding tool rather than a mutating action. It enumerates the topics covered and provides a negative usage rule, though it does not explicitly state side effects or return shape.

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, followed by covered topics and then usage guidance. It is compact and every sentence contributes useful selection or invocation context.

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 zero-parameter onboarding/explanation tool with no output schema and no annotations, the description supplies enough context about what the tool explains and when to use it. Nothing essential for correct invocation is missing.

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?

The tool takes zero parameters, so there is no parameter semantics burden. The description does not need to compensate for undocumented inputs, and the baseline for a zero-parameter tool is met.

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 uses a specific verb and resource: 'Explain Post & Present.' It also scopes the content to the server overview, affiliate account and MCP credentials, and gift-card checkout methods, so the agent knows exactly what invoking it covers.

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?

It explicitly states when to call it: when integrating a shop, chat, or assistant, or when asked what the server is. It also gives a clear exclusion: leave it unused during a shopper gift conversation, which prevents misuse in the primary flow.

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