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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description's only added behavioral fact is the cost tag (10 credits, Tier 1), which is genuinely useful, but it says nothing about what inputs are needed, what is computed, or any limits. Minimal beyond the structured fields.

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 short and the purpose line is front-loaded, with the group/cost tags earning their place as metadata. However the brevity reflects under-specification rather than disciplined concision, so it is only adequately structured.

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 15-parameter computational tool, one purpose sentence plus tags is thin. The output schema spares it from explaining return values and the annotations cover safety, but it never explains required inputs (birth data) or the meaning of its many options, leaving the agent under-equipped to call it correctly.

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 schema has 15 parameters with only 33% description coverage, and the description adds zero parameter meaning - nothing about the required date/time/latitude/longitude, the ayanamsa/house-system choices, or the compact-mode fields/precision options. With low coverage the description is expected to compensate and it does not.

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 names a specific output (marketing voice and campaign style) but gives no verb and never states that it derives this from a birth chart, nor does it differentiate itself from the many sibling business tools like leadership_style or customer_archetype. 'Element-based' is left for the agent to interpret as astrological elements. It is recognizable but vague.

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 mention of alternatives among the ~15 business_* siblings. The agent gets only a group tag and a credit cost, which do not help it decide whether this tool or another business tool is the right call.

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