faf_conductor

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

Annotations indicate a mutating operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds behavioral context like the 'Sets session context' side effect for the path parameter, but does not detail all implications of import/export beyond the parameters.

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 that conveys the core action, but it is somewhat verbose with punctuation and could be streamlined. It is fairly concise without wasted words.

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?

The description covers the main purpose and key parameters, including the side effect of setting session context. However, it lacks details on what happens during import vs export in terms of file changes, and 'AI interop' is ambiguous. No output schema exists, but the tool is simple enough that the description is mostly adequate.

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 coverage is 100%, so parameters are already documented. The description adds value by noting that the path parameter 'Sets session context for subsequent calls', which is not in the schema description. This additional behavioral detail raises the score above baseline.

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 'Import/Export between conductor/ directory (Google Conductor) and project.faf - AI interop!', specifying the action verb and resource. It distinguishes this tool from siblings by the unique import/export functionality not evident in other 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 implies usage for synchronizing conductor and .faf files but provides no explicit guidance on when to use this tool versus alternatives or prerequisites. The context is clear but lacks when-not-to-use advice.

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