get_site_overview

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. The terms 'canonical' and 'authoritative' add meaningful context that the tool returns a definitive, unfiltered view, which is valuable. It does not discuss potential limitations (e.g., caching, data format), but for a parameterless read operation this is adequate.

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, front-loaded sentence that states the action, the resource, and the rationale. It contains no wasteful filler, and the parenthetical 'Tiramisu AI' is minor and does not detract from clarity.

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?

For a parameterless, straightforward retrieval tool, the description provides sufficient context about what is returned and why. There is no output schema, but the description's explicit mention of 'canonical site overview' and 'authoritative product context' makes the tool's role clear and complete.

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 tool has zero parameters, and the schema already provides full coverage (empty properties). The description doesn't need to explain parameters, and the baseline score for 0 params is 4.

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 uses the specific verb 'Return' and identifies the resource 'canonical site overview', making the tool's function unambiguous. This clearly distinguishes it from sibling tools like get_pricing and get_official_links, which target different data.

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 states the purpose ('so an agent has authoritative product context'), which implies when to use this tool: whenever a definitive overview is needed. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to make a reasonable choice.

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