he_get_home_descriptions

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

With no annotations, the description carries the full burden. It discloses behavioral traits: the tool returns compact fields per locale and 'Flags is_fallback when a requested language has no translation.' The name suggests read-only, but no destructive authority is mentioned. Additional details like auth requirements or rate limits would improve it, but for a read-like tool 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?

Two sentences that are front-loaded with the main purpose. Every word adds value: 'Get a property's description texts by language' immediately conveys the action, and the second sentence explains benefits and 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?

The description effectively covers the tool's purpose, behavior (compact fields, is_fallback flag), parameter defaults, and comparison to a sibling. Even without an output schema, it explains the return structure sufficiently for an agent to use the tool correctly.

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%, so baseline is 3. The description adds value beyond the schema by explaining the output shape ('compact title, good_feature, good_place, other per locale') and the default locales for the 'locales' parameter. This helps agents understand what they will get.

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's purpose: 'Get a property's description texts by language' and specifies the compact fields returned (title, good_feature, good_place, other). It also distinguishes from the sibling tool 'he_get_home' by noting it's cheaper for comparing languages.

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 provides explicit guidance on when to use the tool: 'Single API call — cheaper than he_get_home for comparing languages.' This implies it should be used for language comparisons instead of he_get_home, though it lacks explicit when-not-to-use or alternative conditions.

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