create_publisher

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

With no annotations, the description carries the full burden of behavioral disclosure. It simply says 'Create a new publisher' with no mention of side effects, permissions, required fields, or response behavior. This is a near-tautology and provides no actionable transparency.

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 one short sentence with zero wasted words, but it is under-specified for a tool with 11 parameters and nested objects. It is concise in form but not appropriately sized in content.

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 an 11-parameter creation tool with no output schema, the description is drastically incomplete. It does not mention required fields, defaults, return values, or any contextual information needed to use the tool effectively, leaving the agent to rely solely on the schema.

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 parameter semantics are already well documented in the input schema (e.g., email allows login, domain top-level only). The description itself adds no parameter info, but the schema does the heavy lifting, justifying the baseline score of 3.

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 'Create a new publisher' clearly states the action and resource, distinguishing it from sibling create tools for other entities like create_advertiser. However, it does not explicitly differentiate from related publisher operations like update_publisher or archive_publisher, so it stops short of a 5.

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?

There is no guidance on when to use this tool versus alternatives, what prerequisites exist, or how it relates to other publisher lifecycle tools. The description provides no context for tool selection.

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