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

Annotations already disclose readOnlyHint=false and idempotentHint=false, but the description adds value: it says the platform links the repo/branch and provisions a CI/CD pipeline, revealing side effects beyond a plain record insert. The security warning that the credential must be referenced by name is concrete behavioral guidance.

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 tight sentences, front-loaded with the action and mechanism, then closing with the critical security constraint. No filler and nothing that could be dropped without losing meaning.

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 5-required-param creation tool with no output schema, the definition covers the action, the side effects, and the key parameter constraint. It does not mention post-creation behavior such as first build timing or idempotency, but nothing essential for calling it correctly is missing.

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 the baseline is 3, but the description adds real meaning for repo_credential_name by stressing it is referenced BY NAME and that secret values must never be passed. This clarifies an ambiguity the schema alone does not resolve.

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 (Create) and resource (Application) plus the source (connected git repository) and the side effect (provisions the CI/CD pipeline). It is hard to confuse with delete_application or list_applications, though it does not explicitly name or contrast any sibling.

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 phrase 'from a connected git repository' implies the prerequisite that the repo must already be connected, and the tool name makes its role obvious, but there is no explicit when-to-use/when-not-to-use statement or named alternative (e.g. create_stack, cicd_propose_application_pipeline). Usage is implied rather than stated.

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