Essential Dignities

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no behavioral traits beyond the example request. The description does not disclose any side effects, limitations, or requirements, so it adds minimal value over annotations.

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 concise, with a clear structure: purpose, group, cost, and example. However, the group and cost info could be separated into metadata. The example is helpful but adds length. Overall, it is efficient.

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 tool's complexity (11 parameters, no output schema), the description is insufficient. It does not explain the output structure, interpretation of dignities, or how parameters affect results. The example provides some context but leaves many questions unanswered, limiting an agent's ability to invoke the tool 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?

Schema description coverage is 0%, meaning none of the 11 parameters are documented in the schema. The description does not explain any parameter meanings, only shows an example body. Critical fields like 'houseSystem', 'zodiacType', 'ayanamsaId', and 'cosmogram' are left unexplained, making it very difficult for an agent to know what values to provide.

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 clearly states the verb 'Calculate' and the resource 'five Ptolemaic essential dignities (rulership, exaltation, triplicity, term, face) and debilities for each planet.' It also lists the specific dignities, making the tool's purpose highly specific and distinct from siblings.

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?

The description includes a group tag '[Group: Dignities & Receptions]' implying a category, but no explicit guidance on when to use this tool versus alternatives like 'almuten', 'receptions', or 'disposition_chains'. No when-not-to-use or exclusion criteria are provided.

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