ap_material_get_active

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

With no annotations provided, the description carries the burden of behavioral disclosure. The verb 'Report' signals a read-only inspection, and the description names exactly what data is returned. It does not explicitly state that no project state changes, but for a zero-parameter getter this is a minor omission.

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?

One well-structured sentence leads with the action and resource, then fills in the specific output details and clarifies the terminology ('node-canvas name'). No filler or redundant restatement of the tool name.

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?

There is no output schema, so the description explains the return payload. It is complete for a zero-parameter getter, though it leaves minor edge-case behavior (e.g., behavior when no material is active) to the runtime.

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 tool has zero parameters, so the baseline is 4; there is no parameter meaning left unexplained. The description correctly avoids inventing parameter details that do not exist.

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 ('Report') and resource ('the active material') and precisely enumerates the returned data: the node-canvas name and the nine per-channel paint flags. This distinguishes it from siblings such as ap_material_list, which enumerate materials rather than inspecting the active one.

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 intended use is implied: call this when the agent needs the active material's name or paint flags. However, there is no explicit when-to-use/when-not-to-use guidance or alternative routing (e.g., 'use ap_material_list to see all materials').

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