generate_site_analysis

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

The description discloses that the PDF URL is ready-to-open, valid for ~7 days, and no login needed. Annotations declare readOnlyHint=true, and the description does not contradict this. However, it could mention whether any data is saved or if the generation has side effects.

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 comprehensive and front-loaded with key purpose and usage. It includes examples, usage guidelines, and parameter details. While lengthy, every sentence adds value, but minor trimming could improve conciseness.

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 7 parameters, no output schema, and minimal annotations, the description provides a good overview of inputs and outputs, including the survey object fields and the PDF link. It also gives alternatives. Could briefly explain the survey fields more, but overall sufficient.

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 0% schema description coverage, the description compensates by explaining most parameters (lat, lon, capacity_mw, prepared_for, prepared_by, latency_target) with examples and defaults. However, the 'use_case' parameter from the schema is not mentioned in the description, leaving a gap.

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 clearly states that this tool generates a shareable, branded multi-page Site Analysis PDF for a single lat/lon. It distinguishes itself from the sibling tool 'analyze_site' by specifying that this tool creates a polished client deliverable rather than just a numeric score.

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 states when to use this tool: 'Use when a user wants a SHAREABLE, branded multi-page Site Analysis PDF...' and provides an alternative: 'For just the numeric suitability score (no PDF), use analyze_site instead.' This is clear and helpful.

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