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, so the safety profile is fully covered. The description adds genuine non-annotation context: outputs are 'evidence-linked' and deliberately avoid deterministic outcome claims, which tells the agent how to frame results. It still says nothing about input validation failures or the required date/time plus location-vs-coordinates branching.

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?

It is a single short sentence with no padding, so nothing is wasted, but it is a fragment whose brevity comes from under-specification rather than disciplined compression. Being front-loaded is easy when there is only one clause.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a 10-parameter analysis tool sitting in a dense sibling cluster, the description omits the analysis scope, its topic coverage (the topics enum), the location-vs-coordinates requirement, and any guidance on interpreting 'evidence-linked' results.

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 only 30%: place, timezone, and timezoneOffset carry descriptions, but date, time, name, topics, asOfIso, latitude, and longitude are documented nowhere. The description adds no parameter meaning at all, so it fails to compensate for the coverage gap on a 10-parameter tool with an anyOf location requirement.

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 sentence 'Evidence-linked analyze finance structure without deterministic outcome claims' essentially restates the tool name and title without explaining what a 'finance structure' analysis actually produces (wealth houses? income vs. assets? dasha timing?). It offers no differentiation from close siblings such as analyze_career_structure, analyze_marriage_structure, or analyze_education_structure, which follow the identical naming pattern.

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?

There is no when-to-use guidance, no stated prerequisites (e.g., a chart must already exist), and no routing to or away from alternatives among the ~80 sibling tools. The only framing is the epistemic caveat about deterministic claims, which is a constraint rather than usage guidance.

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