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

With no annotations provided, the description carries the behavioral disclosure burden. 'Inspect' conveys a read-only, non-mutating operation, and the parenthetical names the state it exposes: learned vocabulary, concept bindings, and confidence. It does not mention side effects, but none are implied for a simple inspection tool.

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 a single, efficient sentence with no filler. It front-loads the action and resource, then packs clarifying details into a parenthetical, making it easy for an agent to parse quickly.

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 zero-parameter introspection tool with an output schema, the description is complete: it states what is being inspected and what kinds of information will be surfaced. Nothing else is needed for correct tool selection or invocation.

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 input schema has zero parameters, so the baseline is 4. The description adds conceptual meaning by defining the object of inspection and the categories of content it returns, even though there are no parameters to document.

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 a specific verb, 'Inspect', and identifies the exact resource: 'grounded lexicon acquired via situated interaction'. The parenthetical 'learned vocabulary, concept bindings, confidence' further clarifies what the tool exposes and distinguishes it from siblings like cognitive.inspect_self_model.

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 clearly implies use when the agent needs to inspect the grounded lexicon, but it does not explicitly state when to prefer this tool over related siblings such as cognitive.ground_language or cognitive.inspect_self_model. There are no exclusions or when-not-to-use conditions.

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