pddl_get_domain

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

No annotations are provided, so the description must cover behavioral aspects. The description implies this is a read-only, non-destructive operation, but does not explicitly guarantee safe behavior or mention any side effects, rate limits, or prerequisites.

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 concise with only two short sentences. Every word adds value: the verb 'Get', the resource 'PDDL domain string', the purpose 'used to initialize this session', and the use case 're-reading'. No redundancy.

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 no parameters, no output schema, and zero annotations, the description covers the core purpose and usage well. It explains what the domain is used for and what you can do with it, which is sufficient for a simple retrieval tool. It could mention that it returns the current domain (not a past one), but the completeness is adequate.

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 tool has zero parameters and schema coverage is 100%, so the baseline is 4. The description adds value by explaining the semantics of the return value (PDDL domain string, contains action schemas, predicates, types) which goes beyond the empty schema.

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 'Get the PDDL domain string', which is a specific verb+resource. It also mentions purpose: 'to initialize this session' and lists what can be re-read (action schemas, predicates, types), which helps distinguish it from sibling tools like pddl_get_problem.

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 implies use case: re-reading the domain after initialization. It says 'useful for re-reading action schemas, predicates, and types', which gives context but does not explicitly state when not to use it or mention alternatives from siblings.

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