origin_get_layer_info

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

Without annotations, the description must disclose behavioral traits. It states 'inspect,' implying read-only, but does not confirm it is non-destructive, mention any required permissions, or describe side effects. The lack of detail is a gap for safe invocation.

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, front-loaded sentence with no wasted words. It efficiently conveys the core purpose.

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?

While the tool is simple and has an output schema, the description fails to provide enough context for correct use. Key details like parameter semantics and usage guidelines are missing, making it inadequate for an agent to reliably invoke the tool.

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 input schema has 0% description coverage, and the main description does not explain the 'graph_name' or 'layer_index' parameters. The agent is left to guess what values are valid (e.g., graph title, index base). This is a significant omission.

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 the specific verb 'inspect' and clearly identifies the resource as 'one graph layer, its axes, and plots.' It distinguishes this tool from sibling tools like origin_get_graph_info, which inspects the entire graph, and origin_get_worksheet_info, which inspects a worksheet.

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 implies usage for inspecting a specific layer but does not explicitly state when to use this tool versus alternatives like origin_get_graph_info. No exclusions or prerequisites are mentioned, leaving the agent to infer from the tool name.

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