protocol_orientation

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

ReadOnly and idempotent hints already declare safety. Description adds output count (1-3) and notes 'Free' cost. Could detail parameter effects (e.g., ritual_strip, response_mode) but provides useful context beyond annotations.

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 front-load the core action and usage context. No filler; every word earns its place.

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 no output schema and 6 optional parameters, the description provides sufficient context for a recommendation tool. Lacks return format details but adequate within domain.

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% with detailed parameter descriptions. The tool description adds no additional parameter meaning beyond the schema, meeting baseline 3.

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?

Description clearly states 'Return 1-3 recommended Delx primitives' which is a specific verb and resource. Distinguishes from dumping the whole catalog (e.g., list_ontology_primitives) and positions as first call after discovery.

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?

Explicitly says 'Good first call after discovery' indicating when to use. Implies contrast with catalog dumping but does not name specific alternatives. Clear context with no exclusions.

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