np_camera_capture

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

No annotations are provided, so the description must carry the transparency burden. It hints at output ('descriptor + viability') and 'Last' suggests retrieval rather than a new hardware trigger, but it does not disclose whether the operation has side effects, requires camera hardware readiness, or returns data in a specific format. This is minimal disclosure.

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, concise fragment with no wasted words, but it is cryptic and under-specified. It is not verbose yet it sacrifices clarity for brevity, making it less effective than a slightly longer, clearer description.

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?

With no output schema and no annotations, the description must explain what the tool returns and any behavioral context. It mentions 'descriptor + viability' but does not elaborate on their structure or how they are generated. The parameter is simple, but the overall tool behavior remains unclear.

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 single parameter 'mea' is fully described in the schema with a description and constraints (1-5, default 5). The tool description adds no additional context about the parameter, but the schema coverage is 100%, so the baseline of 3 applies.

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 ('capture') and identifies the resource ('MEA camera'), and it distinguishes from siblings by being the only camera-capture tool. However, 'Last' and 'descriptor + viability' are ambiguous, leaving uncertainty about whether it retrieves the most recent capture or performs a new one and what 'descriptor' means precisely.

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 is given on when to use this tool versus alternatives. The phrase 'Last MEA camera capture' implies it is used to obtain the most recent capture, but there is no explicit context, exclusions, or mention of alternative tools for other capture scenarios.

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