add_project_repo

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

Annotations already declare a non-read-only, non-destructive, non-idempotent mutation, so the safety profile is covered. The description adds real value by disclosing the admin requirement and the important consequence that reference-only repos are left untouched, but it is silent on duplicate-attach behavior (relevant given idempotentHint=false) and on what a successful call returns.

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 short sentences, zero waste, with the privileged nature and the core action front-loaded before the reference-only nuance. Nothing is repeated or padded.

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 five-parameter mutation tool with no output schema and no parameter documentation, the description does far too little: it omits the required ProjectId, the repo identifier format, the role of as_agent, and failure modes. An agent could not confidently construct a call from this text alone.

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 0% across five parameters, and the description only illuminates one of them indirectly (IsReferenceOnly, via the "not modified by the system" sentence). It never clarifies whether GithubRepo is a bare name or owner/name path, why GithubOwner is separate, or what as_agent does, leaving genuinely ambiguous inputs.

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 and resource ("attach a GitHub repo to a project") and the "Admin:" prefix signals the privileged nature of the operation. It is clearly distinguishable from siblings like add_project_board or set_project_slack, though it never names those alternatives explicitly.

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 "Admin:" label implies when the tool is applicable (administrative setup of a project) and the reference-only sentence hints at the design-time vs delivery-time distinction. But there is no explicit when-to-use/when-not guidance or comparison with the other project-configuration siblings.

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