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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool returns (clone URL and authentication instructions) and implies a read-only operation via 'Get', but it does not explicitly confirm no side effects, permission requirements, or error behavior. This is adequate for a simple getter but lacks explicit safety or prerequisite details.

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 two concise sentences: the first front-loads the action (what it gets), and the second adds the usage context. No fluff or unnecessary details, making it efficient and well-structured.

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 simple read-only tool with one parameter and no output schema, the description covers the essential purpose, usage, and expected output at a high level. It lacks details on response structure or prerequisites, but the low complexity makes these gaps less critical, and the description gives enough for an agent to select and invoke it correctly.

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?

The input schema already fully documents the 'app' parameter with a clear description ('App ID (UUID) or subdomain'), giving 100% schema coverage. The tool description adds no additional parameter context, so the baseline of 3 is appropriate per the rubric.

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 that the tool retrieves the Git clone URL and authentication instructions for an app, with a specific use case: helping users set up local development with Git push-to-deploy. This specific verb-resource combination distinguishes it from sibling tools that perform git actions like git_pull, git_push, set_git_remote, or remove_git_remote.

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 provides a clear context for when to use this tool: 'Use this to help users set up local development with Git push-to-deploy.' However, it does not explicitly mention when not to use it or name alternatives, though the differentiation from git action tools is implicit through the purpose.

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