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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds a real behavioral constraint — only broker-permitted content is returned — plus provenance fields, but says nothing about result volume, pagination, or what an empty result means.

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 front-loaded sentence with no padding; the parenthetical enumerating fields is dense but earns its place by clarifying output content. Minor jargon ('BRN') is left undefined.

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?

With no output schema, the description must compensate, and it partially does by naming the fields returned. However, it never explains what a 'guide' actually is, gives no valid values for the opaque 'topic' filter, and doesn't cover result shape — gaps that matter for a two-parameter lookup tool.

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% and the area parameter is richly documented with example names and slugs, so the schema carries the load. The description adds only the loose phrase 'about the area' and gives no extra meaning for the opaque 'topic' filter, so the baseline of 3 applies.

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 identifies a specific resource — broker-attributed facts about an area — and even names the payload fields (author BRN, date, source), so an agent knows this is a broker-sourced content lookup rather than a market-data endpoint. It doesn't explicitly contrast itself with siblings like get_area_snapshot or get_comparables, but the 'broker-attributed' qualifier does most of the differentiation work.

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, no statement of prerequisites, and no mention of alternative tools for area facts. The 'only those published with the broker's permission' clause hints at a scope restriction but does not tell the agent when to prefer this tool over get_area_snapshot.

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