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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description usefully adds that matches come from a fixed 778-page corpus and that results carry provenance and risk-flag labels, but it omits any note on computation cost, chart preconditions, or how the nine houses are derived.

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?

Two tight, front-loaded sentences with no filler; the purpose leads and the output content follows. Minor redundancy in describing return fields when an output schema already exists.

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 9-parameter tool with an anyOf input structure and only 33% schema coverage, the description leaves the most confusing part — how to supply a location versus explicit coordinates — entirely unaddressed. The output schema covers return values, so the return-value sentence is not the missing piece; the input guidance is.

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 33% and the description explains no parameters at all — it never mentions date/time, place, or the place-vs-coordinates (latitude/longitude/timezone) alternative required by the schema's anyOf. With low coverage the description should compensate but adds nothing 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?

States a specific verb+resource ('Matches the chart's nine fixed-house placements to remedy blocks') and a concrete scope ('extracted from the complete 778-page corpus'). It is clearly distinct from generic remedy tools, but it never names or contrasts with close siblings like analyze_remedies or explore_lal_kitab_remedy_catalog.

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 prerequisites, and no alternatives named. The description implies the tool operates on an already-computed chart, but an agent gets no signal on when to pick this over the sibling remedy/catalog tools.

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