sg_property_commission

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

Discloses that rates are market norms (CEA) and not legally fixed, which is useful. However, lacks details on how estimates are derived, if they vary by agent, or any disclaimers about accuracy. No annotations to supplement.

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?

Very concise, front-loaded with 'Estimate'. One sentence plus a few phrases. The 'FREE' at the end is extraneous but not harmful. Could be slightly more structured.

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?

Lacks output description: does not specify if commission is returned as a percentage or amount, or both. With 4 parameters and no output schema, the description should clarify the return format for agent decision-making.

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 75% with 3 of 4 parameters described. The description adds the enum values for property_type (HDB, private, landed) and transaction_type (sale, rental) but does not significantly enhance parameter meaning beyond the schema.

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 clearly states the tool estimates Singapore property agent commission for sale or rental transactions, covering HDB, private, landed. It is distinct from siblings like sg_rental_yield or sg_property_analyze, which focus on other metrics.

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?

No guidance on when to use this vs alternative tools. It does not mention prerequisites, exclusions, or context such as when sg_rental_yield might be more appropriate.

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