thincms_get_navigation

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

No annotations are provided. The description implies a read-only operation ('Get'), but does not explicitly state safety, idempotency, or potential side effects. It lacks details on whether the call requires a site to be active or how it behaves if navigation is empty.

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 extremely concise: two sentences that directly state the tool's output and item structure. No unnecessary words, front-loaded with core purpose.

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?

While the description explains basic output format, it does not specify the exact structure of the arrays (e.g., whether it's an object with 'header' and 'footer' keys). No mention of error conditions or empty states. Given no output schema, more detail would be helpful.

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% for both parameters (siteId, confirmProductionWrite). The description adds no additional meaning or context for these parameters. Since schema coverage is high, 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 clearly states the verb 'Get', the resource 'site's header and footer navigation arrays', and specifies the structure of each nav item (label, type, target). It distinguishes itself from sibling tools like thincms_update_navigation and other get tools by focusing on navigation arrays.

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?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., site must be active) or scenarios where it might not be appropriate. No comparison with similar get tools like thincms_get_page or thincms_get_settings.

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