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

With no annotations provided, the description carries the behavioral disclosure burden. It clarifies that the tool returns a 'recommended sequence' rather than executing actions, and it adds cost information with 'FREE — no payment required.' It does not describe potential limitations, but the core behavior is transparent.

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 concise, front-loaded with the core purpose, and every element earns its place: the main explanation, the cost note, varied examples, and explicit usage guidance. There is no filler or repetition.

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 single-parameter tool with no output schema, the description is largely complete: it explains the input, the kind of output, and when to use the tool. It falls slightly short of full completeness by not stating any limitations or what form the recommended sequence takes.

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 coverage is 0%, so the description must compensate for the bare 'goal' parameter. It does so by explaining that the goal is natural language and supplying four concrete example goals. This makes the parameter's meaning and expected shape clear despite the lack of schema-level documentation.

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 clearly states the verb and resource: 'Describe your goal in natural language and get a recommended sequence of TCG Oracle API calls to accomplish it.' It distinguishes this as an orchestrator/planner tool by saying to use it when unsure which tool to call first or when a multi-step workflow is needed.

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 explicit conditions for use: 'Use this when: you're not sure which tool to call first, or need a multi-step workflow recommendation.' This gives clear context, though it does not explicitly state when not to use it or name specific alternative sibling tools.

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