np_camera_capture

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description's only real addition is 'Last', which weakly implies retrieval of an existing capture rather than a new acquisition, and 'descriptor + viability' which hints at return contents. That is thin added context for a tool whose output has no schema.

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?

It is short, but it reads like a banner label rather than a front-loaded sentence: a platform name, an em dash, and a parenthetical, with no leading verb. Brevity here comes from under-specification rather than tight writing.

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, the description is the only place to explain what 'descriptor' and 'viability' mean and whether a frame is acquired or recalled; neither is explained. The zero-required-parameter design also isn't surfaced, so the agent cannot tell whether omitting 'mea' is valid or what the default 5 means behaviorally.

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% and the single 'mea' parameter is documented with a range and default in the schema, so the baseline of 3 applies. The description adds no additional meaning about the MEA selector or what values map to.

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 names a resource and an action ('MEA camera capture') and hints at the payload ('descriptor + viability'), so the general purpose is inferable. However, it is fragment-like and never states a clear verb such as 'retrieve the most recent frame', and it does nothing to distinguish itself from sensor_visual or other capture-like siblings.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling tools. An agent has to guess whether this triggers a new capture or fetches a cached one, and when to prefer it over sensor_visual.

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