get_campaign_templates

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

No annotations are provided, so the description must carry the behavioral load. 'Get' plus 'built-in' reasonably conveys a safe, read-only fetch of system-provided (not user-created) content, and the output schema covers the return shape, but nothing is said about permissions, caching, or freshness.

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?

A single short sentence with the key scoping qualifier ('by objective') placed where it is read first. Nothing is wasted and nothing is buried.

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 zero-parameter listing tool whose return values are documented by an output schema, the description is nearly sufficient. It misses only the downstream relationship to create_campaign_from_template, which matters for an agent deciding whether to call this first.

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 tool takes zero parameters, so the baseline of 4 applies. The phrase 'by objective' is the only semantic content and is not actionable since no objective argument exists, but this is a natural consequence of a no-arg tool.

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?

States a specific verb (get) and resource (built-in campaign templates) plus the organizing dimension (objective). It does not distinguish itself from the sibling create_campaign_from_template, which an agent would likely need to know about, 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 when-to-use guidance: no mention that these templates are the input to create_campaign_from_template, no exclusions, and no note about whether this is a discovery step versus a listing of already-configured campaigns. 'By objective' hints at a filter concept but no parameter exists to express it.

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