np_camera_capture

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only operation (retrieving the last capture) or a mutable action (triggering a new capture). The terms 'capture', 'descriptor', and 'viability' are undefined, leaving the agent uncertain about side effects or data nature.

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 sentence, making it concise, but it is under-informative. It uses front-loaded terms but does not earn its place by providing sufficient clarity. The brevity reduces its helpfulness.

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 lack of output schema and annotations, the description should explain what the tool returns. Terms like 'descriptor + viability' are not elaborated. The agent cannot infer the output format or contents (e.g., image, numeric data). The tool is simple but still incomplete for reliable 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 already describes the 'mea' parameter as 'MEA selector [1-5]' with defaults and constraints. The description adds no extra semantic meaning beyond the schema, so the baseline score of 3 is appropriate.

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 'Last MEA camera capture (descriptor + viability)' is vague. It does not clearly state a verb+resource combination. The meaning of 'last' is ambiguous—whether it retrieves the most recent capture or performs a new capture. It distinguishes minimally from siblings but lacks specificity.

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?

No guidance on when to use this tool vs. alternatives like sensor_visual or other camera-related tools. The description provides no context about prerequisites, typical scenarios, or scenarios where this tool is recommended or not.

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