twilize

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It doesn't explain what 'propose' means operationally (e.g., does it generate suggestions, require confirmation, modify files?), what permissions are needed, or what the output contains beyond the existence of an output schema.

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 extremely concise at just one sentence with zero wasted words. It's front-loaded with the core purpose and doesn't include any unnecessary elaboration or repetition.

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?

For a tool with 4 parameters (2 required), 0% schema coverage, no annotations, but with an output schema, the description is insufficient. While the output schema may document return values, the description fails to explain the tool's behavior, parameter meanings, or usage context needed for effective agent invocation.

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?

With 0% schema description coverage for all 4 parameters, the description provides no parameter semantics whatsoever. It doesn't explain what 'file_path', 'target_source', 'scope', or 'mapping_overrides' represent, their expected formats, or how they influence the mapping proposal.

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 the action ('scan source and target schema') and outcome ('propose a field mapping'), providing a specific verb+resource combination. However, it doesn't differentiate itself from sibling tools like 'inspect_target_schema' or 'migrate_twb_guided' which might involve similar schema analysis.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or when other tools like 'migrate_twb_guided' or 'apply_twb_migration' might be more suitable for mapping-related tasks.

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