install_policy_gate

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

The description discloses key behaviors: file creation, OIDC authentication (no API key), dependency detection, and auto-provisioning. Since no annotations are provided, the description carries the full burden, and it does well by explaining what happens on first push.

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 very concise: two sentences that cover purpose, authentication, dependency detection, and auto-provisioning. No wasted words.

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 (two optional parameters, no output schema), the description covers the necessary context: what is created, how authentication works, and side effects. It is complete enough for the agent to use 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?

Both parameters are fully described in the input schema (100% coverage). The description does not add any additional semantic meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 the tool writes a specific workflow file (AgentScore Policy Gate) to the repo, with distinctive details like OIDC authentication and auto-provisioning on first push. It distinguishes itself from siblings by focusing on a specific file creation task.

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 implies the tool is for setting up the policy gate workflow, which is a one-time setup. It doesn't explicitly state when not to use it or provide alternatives, but the context of setup is clear.

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