housing_finance_guide

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

Annotations already indicate readOnlyHint=true (safe read operation). The description adds 'DEMO', which signals that outputs may be sample or non-real data, providing useful behavioral context beyond annotations.

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?

The description is very short (one sentence) and front-loads the key topic. No unnecessary words. However, it could benefit from a bit more structure without losing conciseness.

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?

Given that an output schema exists (so return values are documented elsewhere) and annotations are present, the description is adequate but minimal. It lacks information on how parameters affect results and does not differentiate from sibling tools. 'DEMO' is important but other context is missing.

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?

The description does not mention or explain the parameters (income_kes_monthly, property_value_kes). Schema coverage is 50% (only property_value_kes has a description). The description fails to add meaning for the undocumented parameter, leaving a gap.

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 lists topics (mortgages, SACCOS, tenant purchase schemes) but does not state an explicit action verb (e.g., 'provides a guide' or 'gives information'). The label 'DEMO' adds confusion about its actual function. It is implied to be a guide, but purpose is vague.

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 description implies usage for housing finance topics, but does not provide explicit guidance on when to use this tool versus sibling tools (e.g., affordable_housing_guide, rental_market_guide). No when-not-to-use or alternative suggestions are given.

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