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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by naming the returned attributes (id, provider, API integration, default mapping), which matters because no output schema exists; pagination or result-size behavior is not mentioned.

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?

Two dense sentences: the first identifies the resource and its payload, the second gives the actionable next step. No filler, and the identity of the resource is front-loaded.

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 single-filter list tool with no output schema, the description does the heavy lifting on return content and downstream usage, so an agent can chain it into create_traffic_source. Minor gap: nothing about ordering, truncation, or whether the search filter applies to provider as well as name.

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?

Only one parameter (search) and the schema documents it at 100% coverage with 'Filter by name'. The description adds no extra meaning about matching behavior (substring vs exact, case sensitivity), so it neither helps nor harms beyond the schema baseline.

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 the specific resource (platform templates for creating a traffic source) and enumerates concrete examples (Push.House, PropellerAds, Meta, TikTok) plus the fields it returns (id, provider, API integration flag, default parameter mapping). This makes it clearly distinct from list_traffic_sources, which returns configured sources rather than templates.

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?

Explicitly routes the agent downstream: 'Pass a template id as template_id to create_traffic_source', which frames the use case as pre-creation discovery. It does not state exclusions or contrast against list_traffic_sources, but the intended usage context is unambiguous.

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