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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so safety and determinism are fully covered. The description adds the currency context (Philippine pesos), which is useful, but nothing about caching, staleness of price data, or scope of coverage, which matters for cost figures.

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, front-loaded with the resource and followed by the exact content list. Every clause earns its place.

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?

No output schema, but the description enumerates what the caller will receive (rent bands, utilities, deposit, monthly total) and the currency, which is enough for an agent to call it correctly. Missing only currency-conversion or data-recency notes, minor for a read-only reference 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?

One optional lang parameter with 0% schema description coverage, but the enum values are self-explanatory language codes. The description says nothing about the lang parameter or multilingual output, so it neither compensates nor misleads. Baseline 3 for a single trivial parameter.

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?

Specific verb-style resource (cost of living in Dumaguete) with a content breakdown that distinguishes it from siblings like get_dumaguete_facts or get_dumaguete_paperwork. An agent can route to it without ambiguity.

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 content enumeration (rent bands, utilities, deposit, monthly total) makes the trigger condition clear by implication, but it never states when to prefer it over get_dumaguete_topic or search_dumaguete_answers. No explicit alternatives or exclusions.

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