get_dsp_entities_live

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

No annotations are provided, but the description adds the context '[Ads / direct API read]' and states 'Hosted endpoint only; this local stdio server is an introspection stub,' disclosing its stub nature. However, it does not disclose behavior such as data freshness, pagination, or error handling, which would be expected for a read operation.

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 concise: two sentences that front-load the purpose and include a necessary caveat about the stub. No redundant or vague wording; every sentence adds value.

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?

Given the absence of an output schema, the description should explain what the tool returns. It only says it reads 'campaigns, ad groups, and targets' but omits return format, fields, pagination, or any details about the filters parameter. This leaves significant gaps for an AI agent to invoke the tool correctly.

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 covers all 7 parameters with descriptions (100% coverage). The tool description does not add any parameter-specific meaning beyond what is already in the schema, so it provides no extra value for parameter semantics. Baseline 3 applies because the schema is self-sufficient.

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 clearly states it reads 'Live Amazon DSP campaigns, ad groups, and targets,' specifying the verb and resource. It distinguishes from similar tools like get_dsp_advertisers_live by focusing on entity types, though it doesn't explicitly differentiate from get_dsp_performance or other DSP tools.

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 offers no explicit guidance on when to use this tool versus other get_* tools like get_dsp_advertisers_live or get_sp_entities_live. It lacks when-not-to-use or alternative tool references, leaving the agent to infer usage from the name and partial description.

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