github_check_collaborators

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

No annotations provided; description only states the check action. Does not disclose behavior such as return format, authentication requirements, or any limitations.

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 sentences with no wasted words. Front-loaded with the essential purpose, immediately understandable.

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?

No output schema exists; description only states what is checked but does not explain what the tool returns (e.g., list, boolean, or count). Incomplete for an agent to fully utilize the output.

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% already documenting owner and repo. Description adds no additional meaning beyond what the schema provides, fitting the baseline.

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?

Clearly states verb 'check', resource 'outside collaborators with write, maintain, or admin permissions', and detection identifier 'ACC-002'. Distinguishes from sibling tools which focus on other checks.

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?

Implies usage for detecting ACC-002 but provides no explicit guidance on when to use vs alternatives like other github_check_* tools. No when-not suggestions.

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