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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is largely covered. The description nonetheless adds real behavioral context beyond the annotations: webhook keys are deliberately excluded from the response, and the result's id doubles as the git_id consumed by runcloud_deploy_git. That is useful disclosure for a read tool.

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?

It is front-loaded with the returned shape, then the omission caveat, then the id linkage and endpoint. Nearly every clause earns its place, though the raw 'GET /servers/{id}/webapps/{webapp}/git' endpoint string is redundant with the tool name and schema.

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?

With no output schema, the description correctly enumerates the return fields and marks the one excluded field, and explains the id linkage to the sibling deploy tool. An agent has enough to call it and interpret the result; only per-alternative routing guidance is absent.

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 100% and both server_id and webapp_id are documented in the schema, including cross-references to runcloud_list_servers and runcloud_list_webapps. The description adds no further parameter meaning, so the baseline 3 applies.

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 names the specific resource (the Git deployment configured on a web application) and enumerates the fields returned (provider, branch, repository URL, auto-deploy flag, script, atomic flag), so the agent knows exactly what data this read returns. It does not state a standalone verb like 'Get' but the noun scope is precise enough to identify the operation. Differentiation from siblings is partial: it links to runcloud_deploy_git but does not contrast with runcloud_get_webapp or runcloud_get_webapp_settings.

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?

There is no explicit when-to-use or when-not-to-use statement. The strongest guidance is the functional pointer 'The id of the result is the git_id for runcloud_deploy_git', which tells the agent this tool feeds the deploy tool. Usage is implied (fetch Git config) but alternatives are not addressed.

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