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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only a partial inventory of returned fields and says nothing about not-found behavior or response shape, which is the remaining behavioral gap.

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?

A single short sentence fragment with no filler, and the most important element ('One landing') is front-loaded. It loses a point only for omitting the operative verb, which makes it slightly less direct than it could be.

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 by-id getter with no output schema, the description should convey what an agent receives; it lists some fields (URL, push-collection and heatmap settings, notes, group, tags) but not the response structure or failure case. Adequate minimum, but not 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?

There is a single required parameter documented at 100% schema coverage ('Landing id'), so the schema fully carries parameter meaning. The description adds no format, range, or source hint for the id, making the baseline 3 appropriate.

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 is a noun phrase naming the resource ('One landing') plus the fields it carries, which implies a single-record fetch and distinguishes it weakly from list_landings by the word 'One'. However, no retrieval verb or scope statement is given, so the purpose is only inferable from the tool name rather than stated.

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 guidance on when to use this versus list_landings or search, and no mention of what happens when the id does not exist. The agent must infer that this is the by-id lookup path purely from the name.

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