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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: results are scoped to the managing workspace, and spend/installs are 'platform-reported', hinting at externally sourced, possibly lagging data. It does not say whether campaigns without data are included or how results are ordered/paginated.

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?

One dense but front-loaded sentence fragment with no filler; the scope constraint and the returned fields come first. It is telegraphic rather than ungrammatical, so nothing needs cutting.

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 one-optional-parameter read tool with annotations and no output schema, the description covers what is returned and the workspace scope. It leaves gaps an agent would care about: default window behavior, pagination/limits, and ordering. Adequate but not complete.

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?

Schema description coverage is 0% for the single 'window' parameter, so the description carries the burden. 'in the window' usefully ties the parameter to the spend/install metrics, but it never states units (the enum 7/14/30/90/365 is presumably days) or what happens when the optional parameter is omitted. Partial compensation only.

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 names the resource (campaigns scoped to 'this workspace manages') and the payload fields (state, budget, platform-reported spend and installs), so an agent can tell it is a listing tool for campaigns. It does not differentiate from siblings like get_campaign or list_budget_tests, 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 statement of when to prefer get_campaign for a single record, and no mention of prerequisites or alternatives. Usage must be inferred entirely from the resource name.

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