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

With no annotations provided, the description carries the responsibility for behavioral disclosure. It does disclose one meaningful behavior: school-divergent special lagnas are reported under not_computed with a reason rather than guessed. However, it does not address authentication, rate limits, error cases, or mutability, though 'Get' strongly implies a read-only operation.

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?

The description is tightly structured: a one-sentence summary followed by a scoped enumeration of contents and a brief note on edge-case behavior. Every sentence adds useful information, with no filler or repetition.

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?

Given the complexity of the returned data and the absence of an output schema, the description does a good job enumerating the lagna/angle categories and the special not_computed field. It falls slightly short of full completeness by not explicitly describing the response envelope or confirming that only read-only data is returned, but the coverage is strong overall.

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?

The only parameter is chart_id, and schema description coverage is 0%. The description never mentions chart_id or any expected format/value semantics. While chart_id is broadly self-explanatory and the schema provides type and required status, the description adds no param-level meaning and does not compensate for the coverage gap.

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 opens with a specific action and resource: 'Get the chart angles, special lagnas, Arudha padas and Bhrigu Bindu.' It then enumerates the exact constituents (MC/IC/Descendant/Vertex, Bhava/Hora/Ghati/Sree/Indu, AL/A2-A12/Upapada), which makes the tool's scope unambiguous and distinct from sibling chart-data tools.

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 is given about when to choose this tool over alternatives such as get_houses, get_grahas, or get_timeline. The description states what the tool returns but does not mention use cases, prerequisites, or sibling tools. Usage context is only implicit from the tool's name and content.

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