Create Post

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

No annotations provided, so description carries full burden. Explains that posts leave a visible trace and lists resulting effects (closing, labeling, etc.). Lacks detail on error behavior, permissions, or rate limits, but adequately describes primary effects for a mutation tool.

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?

Starts with core purpose, uses bullet list for capabilities, notes an important behavioral side effect, and ends with prerequisite IDs. Every sentence adds value; no extraneous content. Front-loaded and efficient.

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 10 parameters, no output schema, and no annotations, the description covers all parameters through action bullets and mentions required IDs. Minor shortcoming: no mention of response format or error handling, but sufficient for a well-understood mutation tool.

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%, baseline 3. Description goes beyond by mapping parameters to concrete actions (e.g., 'set close=true', 'use force_team=true to override existing team') and clarifies the notification parameter's purpose, adding value.

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?

Description clearly states 'Adds a post to a conversation and optionally changes its state.' It enumerates specific capabilities (close, labels, assign, team, note) and differentiates from siblings which are other create/update actions for different entities.

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?

Provides explicit instructions for obtaining required IDs (list_organizations, list_users, list_shared_labels). Does not specify when not to use or compare to alternatives like send_message, but context makes it clear this is for adding posts with state changes.

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