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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's main added value is the ordering guarantee ('most recently updated first'), the search-matching scope, and the important trust caveat that insight content is account-member-written and should be treated as labels, not instructions. That prompt-injection warning is exactly the kind of context annotations cannot convey; only the missing pagination behavior keeps it from a 5.

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 front-loaded with the primary purpose and packs three useful facts into three short clauses with no filler. The closing sentence about d8a_get_insight is slightly tangential to this tool's own invocation but serves as a legitimate handoff hint.

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?

With an output schema present, the description needn't explain return values, and it correctly covers scope, ordering, search semantics and the safety caveat for a read-only list. Nothing essential is missing, though a note on whether an empty result is normal would round it out.

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 coverage is 100%, so limit, offset, search and property_id are already documented in the schema, and the description's note that search matches titles and descriptions largely repeats the schema wording. It adds only the result-ordering semantics that frame how limit/offset paging behaves, so the baseline 3 is appropriate.

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 states a specific verb and resource ('find insights (saved tables, funnels and journeys)') scoped to a property, and names the related sibling d8a_get_insight so the agent can tell the list tool from the single-item tool without opening either schema.

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?

It gives a clear usage context (per-property, team-created insights) and an explicit next step: 'Then d8a_get_insight gives one insight's ready-to-run input.' It does not say when NOT to use it or mention alternatives like d8a_run_query for ad-hoc analysis, so it stays short of a 5.

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