get_industrial_plate

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions views and markets filter but omits details on pagination (count parameter), data freshness, or what happens when markets is null. The count parameter's role is unexplained.

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 (with Chinese translation) that efficiently conveys core functionality and parameter usage. No fluff, but could benefit from slightly more structure for readability.

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 4 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain the count parameter's behavior, response format, or how markets filtering interacts with stocks view. The agent would struggle to use this tool correctly without additional context.

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%, so the description must explain all parameters. It only covers 'view' and 'markets' partially, leaving 'plate_id' and 'count' undocumented. The enum values for view are implied but not explicitly listed, and markets format is vague.

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 clearly states that the tool retrieves info or constituents for an industrial plate, using 'view' to switch between details and stocks. It distinguishes itself from siblings like get_plate_stocks by specifying 'industrial-plate', though it doesn't explicitly differentiate from similar plate tools.

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 description provides guidance on the two views and optional markets filter, but lacks explicit 'when-to-use' vs alternatives or when-not-to-use. Sibling tools exist for similar plate queries (e.g., get_plate_stocks), but no comparisons are made.

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