feedback.silhouette

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

With no annotations, the description must convey behavioral traits. It only states the output (silhouette) but does not disclose side effects, required permissions, or whether it mutates state. For example, it does not clarify if this modifies the scene or object. The phrase 'the form eye' is ambiguous.

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 very concise (one short sentence) but omits essential information like parameter details, output format, and usage context. It is not front-loaded with the most critical info; it hints at purpose without assisting invocation.

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 three parameters and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., an image path, in-memory data), how the preset angles map to views, or how to integrate results. Among many sibling tools, more context is needed for effective selection.

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 0%, and the description mentions no parameters. It fails to explain what 'preset' options (ortho4, ortho6, orbit4) mean visually, what 'object' defaults to, or how 'res' affects output. The agent gets no added meaning beyond raw schema names.

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 'Flat silhouette from preset angles + proportion/symmetry — the form eye' indicates it generates a flat silhouette from preset angles, focusing on proportion and symmetry. It implies a specific function but lacks explicit verb like 'render' or 'generate', and does not clearly differentiate from sibling feedback tools such as feedback.capture or feedback.turntable.

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 versus alternatives like feedback.capture or feedback.capture_views. The description does not mention prerequisites, context, or when not to use it, leaving the agent to infer applicability.

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