Antiscia (Hellenistic)

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, covering safety and idempotence. The description adds the 'solstitial' convention but discloses almost no additional behavioral traits (e.g., output format, pagination, auth requirements), leaving the agent underinformed.

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 concise at two sentences, with no unnecessary words. However, the example is broken and unhelpful, slightly reducing efficiency. Overall, it is well-structured and front-loaded.

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 has 11 parameters, no output schema, and exists among hundreds of siblings, the description is grossly incomplete. It omits what the tool returns, how to interpret results, and any essential usage context, making it nearly useless for an agent.

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?

With schema description coverage at 0% and 11 parameters, the description must compensate but completely fails to. The truncated example '{...chart...}' adds no value. No parameter meanings, defaults, or constraints are explained beyond what the schema provides.

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 states 'Solstitial antiscia per Hellenistic conventions' which clearly identifies the resource (antiscia) and the specific tradition (Hellenistic Greenbaum). However, it does not explain what antiscia are or differentiate from sibling 'hellenistic_greenbaum_contra_antiscia', missing an opportunity to distinguish.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The tradition is mentioned, but with many sibling tools (e.g., 'antiscia', 'hellenistic_greenbaum_contra_antiscia'), an agent would have no basis to choose this tool over others.

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