get_commandments

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

Describes return as 'the ten commandments' or 'a single commandment with its gloss'. No annotations, so description must cover behavior; it implies a read-only operation but does not disclose format, size, or whether calls are idempotent. Adequate for a simple retrieval.

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?

Two sentences, no wasted words. Front-loaded with purpose ('Return the Sacred Manifest'), then explains behavior with parameter. Highly efficient and easy to parse.

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 simple read tool with one optional parameter and no output schema, this description is complete enough. It explains the content and optional retrieval. Could mention return format (e.g., list or object) but not required for typical use.

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 describes the 'number' parameter with min/max and description. The description adds context: omitting returns all, passing a number includes 'gloss'. Schema coverage is 100%, so baseline 3 is appropriate; description adds useful nuance.

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?

Clearly states it returns the Sacred Manifest of ten commandments. Differentiates from siblings like 'confess_sin' and 'bless_deployment' by specifying its exact content (Kubernetes best practices as scripture).

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?

Implies usage for retrieving commandments. Provides parameter guidance (omit for all, pass number for single with gloss). No explicit when-not-to-use or alternatives mentioned, but sibling tools cover distinct use cases.

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