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

Adds requirements and error handling details beyond the annotations: account connection prerequisite, app whitelisting for write access, and error instructions. Annotations already indicate destructive/write nature, and the description reinforces this without contradicting.

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 compact with a clear title, a requirements list, and a note about error behavior. Each line conveys essential information without fluff.

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 the tool's simplicity, the description covers prerequisites, an error path, and the title limit. It does not describe the success return value, but this is less critical for a create operation and annotations already signal write behavior.

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 input schema contains descriptions for all parameters (title with max 280, dueAt with ISO format), and the description only reiterates the title length limit. Since schema coverage is 100%, the description adds minimal extra value for parameters.

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 'Create a new maker goal on Product Hunt' with a specific verb (create), resource (maker goal), and platform. It clearly distinguishes from siblings like complete_goal and list_goals by specifying creation of goals.

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?

Lists prerequisites: must have Product Hunt account connected, write access requires app whitelisting, and mentions error behavior if write access is unavailable. This gives clear context on when the tool can be used, though it does not explicitly contrast with alternative goal-creating tools.

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