Build a report link

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a meaningful trait beyond that: the tool only builds a URL and the actual report creation happens when the user opens it to confirm, which explains the read-only nature. It still omits auth requirements and error behavior.

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 tight sentences with the core action and the return artifact front-loaded; every clause carries information and there is no filler.

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 no output schema, the description correctly states the return value (a Linking API URL) and the follow-up step (user opens it to confirm), which an agent needs before calling. It is slightly thin on the relationship between sources and template placeholders, but overall adequate for this three-parameter tool.

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 only 33%, so the schema does not fully carry the load. The description maps "blank or copied from a template" to template_report_id and "connected to BigQuery tables" to sources, but restates what the schema already says and adds nothing about report_name or how sources entries pair with template aliases.

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?

Specific verb and resource: builds a Looker Studio Linking API URL that creates a report connected to BigQuery tables. It clearly distinguishes itself from siblings like list_reports, screenshot_report, or run_query, which do not construct a report-creation URL.

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 user opens it to confirm" gives workflow context that this produces a link rather than performing the creation, which is useful. However, there is no explicit when-to-use versus when-not statement, no mention of prerequisites (auth, config), and no routing to alternatives.

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