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

Goes well beyond annotations by disclosing that a live backend record is created, that no authentication is required for public initiation, and that the endpoint is rate-limited to 60 req/min per IP — all material for a mutating, non-idempotent call. The return-value sentence is partly boilerplate ('matched records or computed metrics') and doesn't quite fit a submission endpoint.

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?

Front-loads the purpose well, but the body includes filler: the self-referential 'when you specifically need to execute submit_compliance_inquiry' clause and a generic return sentence that reads like a shared template rather than this tool's actual response shape.

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?

For a public, unauthenticated submit tool with full schema coverage and no output schema, the description supplies the needed side effects, auth posture, and rate limit. Only the response description is under-specified, which is a minor gap given no output schema is declared.

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%, so the schema already documents all five parameters including the service_required enum and the SA phone format. The description only repeats the parameter names with required/optional markers, adding no syntax, format, or example detail beyond the schema — baseline 3.

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?

States a specific verb and resource ('Submits a compliance consultation or quote request') and enumerates the concrete service domains (building plan approval, archive plans, occupancy certificates, fire clearance, SDP, rezoning). It does not differentiate itself from siblings within the purpose statement itself — that routing lives in the usage section — so a 4 rather than a 5.

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?

Explicitly names the exclusion condition and the alternatives: 'Do NOT use this tool when another specialized tool fits better (use estimate_scrutiny_fee or check_zoning_requirements)'. The positive trigger is weaker, though — 'Call this tool when you specifically need to execute submit_compliance_inquiry' restates the name rather than describing the qualifying scenario.

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