add_project_repo

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

With no annotations, the description carries the full burden, and it does add two real behavioral facts: this is an admin-only operation, and reference-only repos are not modified by the system. It omits idempotency, what happens on duplicate attachment, and whether the repo must pre-exist, so coverage is partial rather than complete.

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 core action and followed by the one non-obvious semantic detail. No filler, though it is brief enough that the brevity borders on under-specification.

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?

A mutation tool with no annotations, no output schema, and 5 undocumented parameters needs substantially more: permission details beyond the 'Admin' label, effect on the project, and return/confirmation behavior. The reference-only note is the only substantive addition.

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 5 parameters. The description only indirectly explains IsReferenceOnly (reference-only repos are not modified) and implies GithubRepo/GithubOwner via 'GitHub repo'; ProjectId and as_agent are left entirely undocumented, so the description does not compensate for the coverage gap.

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', plus an 'Admin:' scope qualifier that frames the privilege level. It is distinguishable from siblings like create_project or add_project_board, though it never names an alternative 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?

There is no when-to-use / when-not-to-use guidance and no alternatives named. The reference-only clause hints at a scenario (upstream project used as a design reference) but frames it as a behavioral note rather than a selection rule, so an agent gets no routing help among the many project-related siblings.

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