sftp_vincular_repositorio

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds real value by disclosing the on-disk layout that results from the call, but it does not say whether missing directories are created, whether an existing link is overwritten, or what validation occurs on the git repository.

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 short sentences, front-loaded with the purpose and followed by the storage layout and the sourcing instruction. Nothing is redundant, though the final sentence is slightly vague about what 'o caminho que o usuario informou' should look like.

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 two-parameter configuration tool with no output schema, the definition covers intent and resulting layout adequately, and annotations supply the mutation profile. It still leaves the agent guessing about directory creation, path format, and overwrite/validation behavior, which matter for a write operation.

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%, so the description must carry the burden. It does partly: the path template <repositorio>/.claude/sftp/<perfil>/ implies that 'perfil' selects a subfolder and that 'caminho_repositorio' is the repository root. However, it never states whether the path must be absolute, whether it must already exist, or what format 'perfil' takes.

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?

States a specific verb and resource: it defines/links the client's local git repository and explains that downloads, backups and profile audit live under <repositorio>/.claude/sftp/<perfil>/. That is a clear purpose that separates it from siblings like sftp_cadastrar (registration) or sftp_baixar (download), though the description never names those siblings explicitly.

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?

Usage is only implied: 'Use o caminho que o usuario informou' tells the agent where to get the path but not when to call this versus other setup tools, nor any prerequisites. There is no statement about whether the repository must already exist, whether git must be initialized, or what happens if a link is already configured.

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