Project Graph Insights

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

Annotations already indicate readOnlyHint=true, openWorldHint=true, and destructiveHint=false, and the description's 'fetch' wording is consistent with read-only behavior. The description does not add meaningful behavioral context beyond the annotations, such as how open-world resolution or generated links behave.

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 a single, front-loaded sentence with no filler. It is appropriately concise, though it leans on the enum values for semantic weight and does not use the space to clarify sibling distinctions.

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?

An output schema exists and annotations cover the safety profile, reducing the burden on the description. Still, the description is minimal for a tool with eight parameters and many overlapping siblings; an agent cannot tell how the 'overview' focus relates to projects_overview or when impact analysis needs resourceId.

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 75%, so most parameters are documented in the schema. The description adds the 'graph intelligence' framing and repeats the focus enum values, but it does not clarify limit semantics, which focus requires resourceId, or the meaning of syncVersion beyond what the schema already provides.

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 uses a specific verb and resource: 'Fetch graph intelligence' and enumerates the main focus areas. It is clear about what the tool does, but it does not explicitly differentiate it from sibling tools like projects_overview or projects_graph_get.

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 focus list implicitly signals when the tool is relevant, e.g., for overview, impact, security, cost, or changes. However, there is no explicit guidance about when to choose this tool over the many graph-related siblings, nor any stated alternatives or exclusions.

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