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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering safety and repeatability. The description adds one behavioral claim ('without deterministic outcome claims'), which is a useful constraint but only weakly one: it tells the agent not to expect definitive predictions but doesn't explain what evidence linkage looks like, what output format is produced, or whether topics filter the analysis.

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?

A single short sentence with no filler, front-loaded with the verb. It's efficient, though the efficiency comes partly from under-specification rather than tight writing.

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 tool has 10 parameters, an anyOf location constraint, and sits among 40+ analysis siblings, but the description provides no help navigating any of this. Even with an output schema available (reducing the need to explain returns), the description is too thin to help an agent choose this tool or supply correct inputs.

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 only 30%, so the description must compensate for undocumented parameters, yet it adds nothing about 'topics', 'asOfIso', 'date', 'time', or 'name'. With 10 parameters and a required anyOf constraint (place OR lat/long/timezone), the description leaves all the parameter semantics to the schema, which is incomplete. This is below the baseline because the description fails to compensate for low coverage.

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 'Evidence-linked analyze property and vehicle without deterministic outcome claims' essentially restates the tool name 'analyze_property_and_vehicle' with a methodological qualifier. It does not distinguish this tool from the many sibling analyze_* tools (analyze_chart_topic, analyze_house, analyze_varga) that also perform property-focused analysis. While it does mention 'property and vehicle', it's unclear what analysis beyond the name is actually performed.

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 when-to-use guidance is provided. The description does not state when to select this tool versus analyze_chart_topic, analyze_house, or any of the other ~40 analysis siblings. No alternatives, no prerequisites, no exclusions.

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