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

Goes beyond the readOnlyHint/openWorldHint annotations by disclosing the ordering (most recently updated first), what the search field actually matches, and a prompt-injection caveat that saved report text is member-authored and should be treated as labels, not instructions. That untrusted-content warning is behaviorally important context annotations cannot convey.

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 but purposeful sentences: purpose and ordering first, then the safety caveat, then the next action. No padding or redundant restatement of the tool name.

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?

Output schema exists so return shape need not be described, and the description supplies the discovery-to-detail workflow, result ordering, and the untrusted-content handling rule. Nothing an agent needs to call it correctly is missing.

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 all documented in the schema. The description only restates that search matches titles and descriptions, adding no new syntax or constraint detail. Baseline 3 applies when the schema does the heavy lifting.

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 a specific verb and resource ('find reports the team already saved for a property') and names the covered report types (tables, funnels, paths). It also distinguishes itself from the sibling d8a_get_saved_report, which returns one report's input, so an agent can route 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?

Explicitly gives the use case and the follow-up step: use this to discover saved reports, then call d8a_get_saved_report to get ready-to-run input. It stops short of stating when not to use it (e.g., ad-hoc queries via d8a_run_query), so it is clear but not exhaustive.

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