Add Table Join

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

With no annotations, the description must disclose behavioral traits, but it only states the action without explaining side effects (e.g., whether the join is saved to the project or modifies data). The description adds no behavioral context beyond the bare action.

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, but conciseness must not sacrifice necessary information. It fails to include parameter details, usage context, or behavioral notes, making it under-specified rather than efficiently complete.

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 the tool has 5 parameters requiring detailed explanation (especially with 0% schema coverage), no output schema, and siblings to differentiate, the description is drastically incomplete. It lacks any context about what a table join entails in QGIS or how parameters interact.

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%, yet the description provides no explanation of any parameter. The agent cannot understand what 'target_field', 'join_field', or 'prefix' mean or how they relate to the join operation.

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 states the verb 'Add' and the resource 'table join' applied to 'vector layer', making the core action clear. However, it does not distinguish this from the sibling tool 'spatial_join', which could cause confusion for an agent deciding which to use.

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 is provided on when to use this tool versus alternatives like 'spatial_join', nor are prerequisites or exclusions mentioned. The agent is left guessing about appropriate contexts.

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