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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds only metadata (group, endpoint, cost) but nothing about behavioral traits such as what the response contains, pagination, or error conditions. For a read/compute tool with annotations in place, this is thin but not contradictory.

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 short and front-loaded with the key concept. The bracketed metadata block (group, endpoint, cost) adds operational utility without bloat. It's efficient, though the core sentence could be more action-oriented.

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?

The tool has an output schema, so return-value explanation isn't required. The description covers group, endpoint, cost, and alias relationship, but omits what the tool actually computes and when to use it relative to the many profection/time-lord siblings. Adequate but with notable gaps.

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 100%, so the schema fully documents parameters including timezoneOffset, houseSystem, targetAge, and fields/precision. The description adds no parameter meaning beyond the schema, so the baseline 3 is appropriate.

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 reads 'Annual profection year-lord with full classical condition,' which tells the agent what the output is but not what the tool does as an action. It's close to a restatement of the title/name rather than a verb+resource statement. It does not distinguish itself from siblings like astroway_prognostics_profections or astroway_hellenistic_brennan_time_lord_stack.

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 provides no when-to-use guidance, no alternatives, and no exclusions. The only routing hint is the note that it is a 'Cursor-friendly alias' for astroway_hellenistic_brennan_profections_detail, which is about naming, not usage selection.

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