pddl_init

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It only states that initialization must happen first but does not disclose what the tool does internally (e.g., whether it clears previous state, if it validates the domain/problem, or what side effects occur). For a setup tool, the agent needs to know session lifecycle details.

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 consists of two short, direct sentences. The first states the action and inputs; the second gives critical ordering guidance. There is no redundant or extraneous text.

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?

The tool has no output schema and no annotations, so the description must explain what happens after initialization. It does not mention return values (e.g., success confirmation, session ID, or error messages). For a simple init tool, this is adequate but leaves the agent uninformed about the result of the call.

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 description coverage is 100%, so baseline is 3. The description merely restates 'domain and problem' without adding any additional semantics (e.g., format expectations, size limits, or hints about PDDL syntax). It adds no value beyond what the schema already 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 uses the specific verb 'Initialize' and identifies the resource as a 'PDDL exploration session'. It lists the required inputs (domain and problem) and implicitly distinguishes from the sibling tool 'pddl_init_from_files', which appears to be an alternative initialization method. This is a precise and clear purpose statement.

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 explicitly states 'Must be called first before using other tools', providing clear usage order. However, it does not explain when to prefer this tool over 'pddl_init_from_files' or describe any prerequisites or conditions for calling it. This is a clear context but lacks exclusions or alternatives.

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