analyze_site_structure

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

With no annotations, the description carries the full burden. It explains what the tool computes but does not disclose output format, side effects, or dependencies (e.g., whether a prior crawl is strictly required if no sessionId is provided). The behavior is not contradictory or misleading, but it lacks details about return values or potential errors.

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 a single, concise sentence that lists the main functions without extraneous information. It is well-structured and easy to parse, covering all key aspects of the tool's behavior.

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?

The description provides a clear functional overview and the parameter is explained, but it does not mention the output type (e.g., report, JSON) or any prerequisites like the need for a completed crawl. Given the sibling tools and the implicit session context, it is fairly complete but could be more explicit about expected outputs and prerequisites.

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?

The sessionId parameter is described beyond its type: it is a scan session ID, and if left blank, the most recent session is used. This adds meaningful context. It could be improved by specifying the format or an example, but the description is sufficient for a single optional parameter.

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 the tool's function: automatically building a site hierarchy tree, analyzing URL depth distribution, detecting orphan pages, and counting top linked pages. It is specific and distinct from sibling tools like crawl_website or audit_seo_issues, making its purpose unambiguous.

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 does not explicitly mention when to use this tool versus alternatives like audit_seo_issues or classify_content_topics. However, the parameter for sessionId implies it should be used after a crawl session, and the default behavior (using the most recent session) gives implicit guidance. It could be improved by explicitly stating that this tool is for structural analysis after crawling.

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