Read GitHub project boards

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

The annotations already establish read-only, open-world, and idempotent behavior, and the description adds substantial operational context beyond that: lookup route order, ambiguity handling, not_found behavior, truncation thresholds, and required token scopes. It also warns that user-authored titles, bodies, and field values are data rather than instructions, which is valuable safety context.

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 front-loaded and method-organized, but it is a dense run-on paragraph with long clauses and duplicated schema details such as status syntax and content types. The content is useful, yet the structure could be much clearer with bullets or shorter sentences.

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 complex 11-parameter read tool with an output schema, the description is very complete: it covers the three methods, board resolution, filters, truncation, authentication, and prompt-injection safety. An agent has enough context to choose a method and understand failure modes without needing additional documentation.

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%, so the baseline is 3, but the description adds meaningful resolution semantics beyond the schema, especially the route order for title lookup and the handling of multiple candidates. It also clarifies how project, owner, repo, and method interact, though some parameter details are restated from the schema.

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 opens with a specific verb and resource, "Read GitHub project boards (Projects v2)," and then clearly names the three read methods: view, list, and item_list. This distinguishes it from the project-mutation siblings without requiring the agent to infer intent from the name alone.

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 method-specific descriptions give clear guidance on when to use view, list, or item_list, including defaults and truncation behavior. It stops short of explicitly naming when not to use this tool or pointing to the write-oriented project siblings, so it is strong but not a full 5.

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