coolify_list_github_app_repositories

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

Without annotations, the description carries full burden for behavioral disclosure. It only says 'List all repositories' and gives input guidance, but does not mention whether the operation is read-only, if authentication is required, if results are paginated, or any side effects. The description adds minimal behavioral context beyond the obvious list operation.

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, front-loads the main purpose, and has no unnecessary words. Every sentence adds value.

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?

Given the simplicity of the tool (1 param, no nested objects, no output schema), the description is mostly adequate. However, it does not describe the return format or whether it returns metadata like names, URLs, or other properties. For a list tool, agents might benefit from knowing what fields are returned, but the lack of output schema makes this incomplete.

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 schema already describes the parameter well (GitHub App numeric ID from coolify_list_github_apps response), and the description adds 'not the uuid', which is a helpful clarification not in the schema. With 100% schema coverage, the baseline is 3, and the extra nuance makes it a 4.

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 'List all repositories accessible by a GitHub App', using a specific verb and resource. It also distinguishes itself from sibling tools by specifying the source of the required id ('from coolify_list_github_apps') and contrasting with uuid, making the purpose unambiguous.

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 explicitly says to use the numeric id from coolify_list_github_apps and not the uuid, providing a clear prerequisite and avoiding a common pitfall. However, it does not state when this tool should be used over alternatives or when it should not be used, so it is not a perfect 5.

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