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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral context the annotations don't: the tool is a quiz-style ranking and returns a percentage match, which tells the agent what kind of output to expect. It says nothing about how traits are combined, defaults, or scoring sensitivity.

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 tight sentences, zero waste. The core behavior (ranking by fit with a % match) is front-loaded before the usage cue.

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 return format is at least characterized ('% match' ranking), which matters given there is no output schema, and the read-only nature is covered by annotations. But with six all-optional parameters and no output schema, the definition should explain default behavior when no criteria are provided and roughly what the ranking looks like.

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 only 33%, so the description should compensate more than it does — it only generically maps to 'a way of life and a budget'. Four of the six parameters are self-describing enums (sea, pace, persona, israeli_community) whose values speak for themselves, which keeps this at a baseline rather than below it, but there is no explanation of how the traits interact or what happens when none are supplied despite zero required parameters.

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 a specific verb and resource: a neighbourhood quiz that ranks neighbourhoods by fit to a way of life and budget with a % match. That is concrete and distinct from the sibling tools (budget_calculator, purchase_costs, search_projects), though it never explicitly states how it differs from search_projects by name.

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?

Gives a clear triggering condition: 'Use for where should I live/buy questions.' That is a real usage cue rather than an implied one. It does not, however, name an alternative or say when another tool (e.g. search_projects) should be preferred instead.

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