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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context in the form of group and cost (10 credits, Tier 1), but does not describe output behavior, auth needs, or other operational traits.

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 very short and front-loads the only substantive phrase before the metadata tags. It is concise and structured, though the brevity comes at the cost of clarity and completeness.

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?

With 15 parameters, 33% schema description coverage, many sibling tools, and no explanation of the Rudhyar personality keynote concept, the description is too thin. The output schema removes the need to document return values, but the description still lacks the context needed to invoke this complex 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?

The schema has 15 parameters and only 33% description coverage, leaving many parameters undocumented even in the schema. The description provides no parameter guidance at all, so it fails to compensate for the low schema coverage.

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 essentially restates the tool name/title: 'Single-keynote signature for the chart' adds little beyond 'Rudhyar: Personality Keynote.' It does not explain what a keynote is or distinguish this tool from the similarly named sibling astroway_psyr_personality_keynote.

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 guidance on when to use this tool, when not to use it, or which sibling tools are alternatives. The group and cost tags do not tell an agent when this specific Rudhyar personality keynote should be selected.

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