campaigns_get_state

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

With no annotations, the description must disclose behavioral traits such as read-only nature, permissions, or side effects. It simply says 'Get campaign state', offering no information beyond the implied read operation, leaving the agent without crucial safety and effect details.

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?

Although the description is short, it is under-specified and simply repeats the tool name. It does not add value, making it an inefficient use of the description field rather than a concise, informative statement.

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?

Despite having an output schema and a single parameter, the description lacks context about what 'state' includes, when to use this tool, and how it differs from related campaign tools. This incompleteness hinders correct selection and invocation, especially among many sibling tools.

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 one required parameter 'campaign_id' with 0% schema description coverage. The description does not explain the parameter's meaning, format, or how to locate it, failing to compensate for the missing schema documentation.

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 'Get campaign state' is essentially a restatement of the tool name 'campaigns_get_state', making it tautological. It does not elaborate on what 'state' encompasses or distinguish this tool from siblings like 'campaigns_describe'.

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?

The description provides no guidance on when to use this tool versus alternatives. It only states the action without any context about appropriate scenarios, prerequisites, or exclusions.

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