dap_domain_report

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the source (Digital Analytics Program) and domain scope, but does not disclose other behavioral traits like date filtering, pagination, or response format. It does not contradict annotations.

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 two sentences plus a succinct example. It is front-loaded with the core purpose and contains no fluff, making it highly efficient.

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 a well-documented schema and readOnlyHint annotation, the description provides enough context for use. The example adds practical guidance. Without an output schema, some return-structure information is missing, but the tool's nature as an analytics report is reasonably clear.

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% with descriptions for all six parameters. The description's example (domain='nasa.gov', report='browser', limit=50) illustrates typical usage but does not add meaning beyond the schema's parameter descriptions, so 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 opens with 'Get a domain-specific web analytics report from the Digital Analytics Program,' which is a specific verb + resource pair. It also states 'Returns analytics data for a specific government website domain,' clearly distinguishing this from sibling tools like dap_gov_wide_report and dap_agency_report.

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 provides clear context for when to use this tool (for a specific government website domain) via 'domain-specific' and 'specific government website domain.' However, it does not explicitly mention alternatives or when not to use it, so it stops short of full exclusion guidance.

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