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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, covering the full safety profile. The description adds essentially nothing beyond that: it does not describe result ordering, how partial matches behave, pagination, or what happens when the default limit of 15 is exceeded. A simple read tool with complete annotations needs little, but this adds no new behavioral context.

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 short sentences with zero filler; the core action is front-loaded in the first sentence and the parenthetical examples are compact. Nothing is wasted.

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 simple two-parameter read tool with 100% schema coverage and no output schema, the description is close to sufficient: the agent knows the source, the filter, and the input shape. Only the result shape (ordering, typical payload size) is left implicit, which is a minor gap given the tool's simplicity.

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 description coverage is 100%, so both parameters (continent and limit) are already fully documented in the schema, including the default of 15. The description's continent examples duplicate the schema's examples rather than adding format constraints or matching semantics. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ('Returns stays from the NomadStays database filtered by continent'), so the agent knows exactly what it retrieves. However, it never distinguishes itself from the many sibling filters (getStaysByCountry, getStaysByLocation, getStaysByBudget), so the agent must infer which filter applies.

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?

'Search by continent name' implies the usage context and the examples ('Europe', 'Asia', 'Africa') show expected input, but there is no stated when-to-use or when-not-to-use guidance relative to the sibling country/location/budget filters. Usage is implied rather than explained.

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