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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the credit cost (10 credits, Tier 1) and its group, which is genuinely useful behavioral context for an agent deciding whether to invoke. It does not add anything about output shape, but annotations lower the bar.

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 terse and front-loads the core meaning before the metadata tags. Every line carries some signal, though the cryptic 'JWG' token is wasted space for a general agent. Appropriate size for the content provided.

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 natal chart tool with a required date/time/coordinates core, the description gives the agent nothing about required inputs or the computation context. An output schema exists so return values need not be explained, but the input-side incompleteness leaves the agent under-informed.

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?

15 parameters with only 33% schema description coverage, and the description supplies nothing about any parameter. Several key inputs (date, time, latitude, longitude, zodiacType, houseSystem) are undocumented in both places. The description fails to compensate for the coverage gap on a complex 15-param tool.

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 the tool's outputs (Pluto sign, house, ruler, hard aspects) which is more specific than the title alone and helps distinguish it from evolutionary siblings like nodal_axis_detail or skipped_steps. However, there is no verb describing the operation, and the cryptic 'JWG' prefix (Jeffrey Wolf Green) is opaque to an agent without domain expertise. Purpose is inferable but not stated cleanly.

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 routing to alternatives. The [Group: Evolutionary Astrology] tag loosely places it in a family but does not say when to pick this Pluto tool over the several other evolutionary tools. No usage context is provided.

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