get_websites

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

With no annotations, the description bears full burden. It discloses it lists data without arguments and conditionally returns team or personal websites. It does not detail return format or side effects, but 'list' implies read-only. Adequate for a non-destructive 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?

Three concise sentences. Front-loaded with purpose. Every sentence adds value: what it does, how to use returned ID, and conditional behavior. No wasted words.

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?

Low complexity with zero parameters and an output schema present. Description covers purpose, usage, and conditional behavior fully. Agent can confidently determine when and how to use this 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?

There are zero parameters, so baseline is 4. Description adds value by stating 'Takes no arguments,' confirming 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?

Description clearly states 'List the websites in your Umami account, with their ids, names, and domains.' The verb 'list' and resource 'websites' are specific. It distinguishes from sibling tools like get_active_visitors and get_website_metrics by focusing on listing basic website info.

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?

Description explains it takes no arguments and instructs to use returned id for other tools. It clarifies team vs personal website retrieval based on configuration. No explicit when-not-to-use, but the context is sufficient for a simple tool.

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