create_demand_source

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely restates the action without revealing any side effects, required permissions, validation rules, or what happens on success. The schema hints at default status and allowed networks but the description itself communicates nothing beyond 'creates something'.

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 very brief, but it is under-specified rather than economically useful. It essentially restates the tool name and supplies no additional context, failing to earn its place as a valuable explanatory sentence.

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 create operation with 7 parameters, 2 enums, and no output schema, this one-sentence description is inadequate. It does not explain what a demand source is, what constraints exist, what the expected response is, or how this tool fits into the broader workflow.

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 has 100% parameter description coverage, so the schema already provides meaning for every field. The description adds no parameter-level insights beyond what is in the schema, thus the baseline of 3 is appropriate.

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 demand source' uses a clear verb+resource pattern, making the tool's function immediately obvious. It also distinguishes from related tools like update_demand_source, get_demand_source, and create_demand_endpoint by specifying the exact resource type.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as whether an advertiser or publisher must exist first, nor any note about related operations like create_demand_endpoint. The description leaves the usage context entirely implicit.

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