Carcer — Prison

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds no further behavioral context (e.g., what 'Restriction' means in practice, permissions needed, or if it returns textual analysis vs. data).

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 extremely short but not concise in a helpful way; it lacks clarity and important details. The group annotation is minimal, and the example is empty.

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 no output schema and no description of return value, the agent cannot anticipate what the tool returns. The description fails to compensate for the missing output schema and incomplete parameter example.

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 only parameter 'body' has a schema that refers to an example in the description, but the description provides only 'Example request body: {}' with no actual fields. This leaves the agent without guidance on required or optional properties.

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 uses abstract terms 'Restriction, confinement, isolation' without a verb, leaving the agent unsure if the tool interprets, generates, or analyzes the Carcer figure. It relies on the name 'geomancy_carcer' for context, but lacks specificity.

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 on when to use this tool versus other geomancy_* tools. The agent is given no criteria to distinguish Carcer from related figures like geomancy_acquisitio or geomancy_albus.

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