get_theme_structure

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

No annotations provided; description states it fetches public page and stylesheets, implying a safe read operation. Lacks details on error handling or authentication, but adequate for a read-only tool.

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 sentences, front-loaded with purpose, no redundant words. Every phrase adds value: purpose, method, and usage guidance.

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 the tool's simplicity, the description covers the essential aspects: what it does, how to invoke (path vs blog_url), and when to use (before restyling). Output schema exists, so return values don't need elaboration.

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% (baseline 3). Description adds value by explaining why 'path' matters (different templates) and gives examples ('/', '/my-post/'), aiding correct usage beyond the schema.

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 'inspects a live Ghost page and returns its markup and CSS' with a specific verb and resource. It distinguishes itself from siblings like 'preview_theme' or 'download_theme' by focusing on fetching rendered page structure for styling.

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 advises passing the correct path because homepage and posts use different templates, implying use before restyling. No explicit exclusions or alternatives, but context is clear.

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