Get Tehran landing

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without description help. The description adds only that the payload contains categories and highlighted filters; it says nothing about whether the content is static, localized, or region-locked, which matters for an open-world hint. Useful but thin beyond the annotations.

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?

Seven words with no filler, so nothing is wasted, but the terseness is under-specification rather than discipline. The one clause present is not front-loaded with an action or scope statement that would orient an agent.

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?

There is no output schema, so the description is the only source for what comes back, and "categories and highlighted filters" is too abstract to tell an agent the shape, identifiers, or how to act on the result. For a zero-parameter content-fetch tool whose only job is returning structured data, the return contract should be spelled out.

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 takes zero parameters, so there is nothing for the description to disambiguate. Per the baseline rule for a parameterless schema, this scores 4; the description does not need to compensate for any coverage gap.

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?

Names the resource (Tehran landing) and hints at its contents ("categories and highlighted filters"), but "landing" is internal jargon with no verb and no explanation of what a landing payload actually is. An agent can guess it is a Tehran-specific content block distinct from sh_search_destinations, but only by name similarity, not by any stated scope.

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?

There is no when-to-use guidance at all: nothing says whether this is a discovery entry point, a UI-configuration payload, or a prerequisite for the search tools. Siblings like sh_list_search_filters and sh_search_destinations could plausibly cover the same need, and the description gives no rule for choosing between them.

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