Midpoint Pictures

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

The description does not contradict annotations but provides no behavioral context beyond the cryptic phrase. It does not explain what 'A=B/C structures' entail or what the tool returns, leaving the agent without essential behavioral insights.

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 but not effectively concise; the cryptic content and irrelevant example waste space without conveying necessary information.

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 12 parameters, no output schema, and the specialized cosmobiology domain, the description is severely incomplete. It fails to clarify key concepts like 'A=B/C structures' or 'sentence form', making the tool almost unusable for an AI.

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 0% schema description coverage, the description offers no explanation for any of the 12 parameters. The example mentions a 'chart' field not present in the schema, misleading the agent about valid inputs.

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 'A=B/C structures with sentence form' is cryptic and does not clearly state what the tool does. The example request body includes parameters not in the input schema, adding confusion. It mentions the cosmobiology group but fails to specify the tool's function.

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 guidance is provided on when to use this tool versus its siblings, such as cosmobiology_cosmogram or cosmobiology_dial_90. There is no context about appropriate scenarios or alternative tools.

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