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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so most of the description's content is redundant. 'No spend' is the only added detail, and it is ambiguous (no cost incurred vs. no spend data returned); the trailing 'Fields: soclo://tools/...' reference conveys nothing actionable.

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 sentences are short and the core purpose is front-loaded, but the third sentence ('Fields: soclo://tools/soclo_ads_get_ads_timeline') is dead weight for an agent and the middle sentence mostly duplicates the annotations.

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 tool with a nested date-range object, six parameters and no output schema, the description omits date-range format/behavior, account vs ad-account scoping, and what the daily metrics contain. Given the annotations already cover safety, the missing pieces are precisely the ones only the description could supply.

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?

With 6 parameters at 50% schema description coverage and an undocumented nested 'parameters' object (fromDate/toDate), the description must compensate but supplies no parameter information at all. The only hint is the word 'daily', which weakly implies a date range; the opaque URI adds no semantics.

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 restates the title almost verbatim ('Get daily account metrics') with no meaningful elaboration. It does not distinguish this timeline query from adjacent read tools such as soclo_ads_get_ad_analytics, soclo_ads_query_ad_insights, or soclo_ads_get_campaign_analytics, so an agent cannot confidently route between them.

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?

'Read only; no spend' hints at the safety profile but gives no when-to-use guidance and names no alternatives. Nothing tells the agent under what conditions to pick a daily timeline over the other analytics tools in this large sibling set.

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