Add Layout Table

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

Discloses max_rows caps features and position/size units (mm), but lacks details on error handling, required permissions, or behavior when layer_id is invalid. With no annotations, more transparency is needed.

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?

Two concise sentences with no redundant information. Front-loads the core purpose and key parameter behavior.

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 0% schema description coverage, no output schema, and 7 parameters, the description is too brief. It omits error conditions, required layer type, and default behavior. Incomplete for effective tool usage.

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?

Description adds meaning for max_rows (capping) and position/size (mm units), but does not explain x, y, width, height defaults or the roles of layer_id and layout_name beyond being required. Schema coverage is 0%, so description must compensate more.

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?

Description clearly states the tool adds an attribute table for a vector layer to a print layout, using specific verb and resource. It distinguishes from sibling tools like add_layout_label or add_layout_map by specifying 'attribute table' for vector layer.

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 (e.g., add_layout_label for labels). No prerequisites or exclusions mentioned.

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