project

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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal that map returns normalized connectivity in structuredContent.map and that includeRaw adds the original graph payload, offering useful context. However, it says nothing about side effects, permissions, or behavior of the other operations (list/get/metadata/flow).

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 only two sentences, front-loaded with the core purpose ('Project ops') followed by a focused detail on map. Every phrase contributes distinct information, and it is appropriately compact.

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 lack of annotations and output schema, the description needs to compensate, but it only elaborates on the map operation. List, get, metadata, and flow are left completely unspecified, with no information about return formats, error behavior, or prerequisites. For a multi-operation tool, this is significantly incomplete.

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?

The input schema is empty (0 parameters), so baseline is 4. The description adds meaning by mentioning the includeRaw option for map, which is not present in the schema. This goes beyond the schema and provides parameter semantics that would otherwise be entirely undocumented.

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 identifies the resource ('Project ops') and enumerates specific operations (list/get/metadata/flow/map), distinguishing it from sibling tools focused on other resources. However, verbs like 'flow' and 'map' are not fully elaborated, leaving some ambiguity.

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 this is the tool for project operations but provides no explicit guidance on when to use it versus alternatives, nor does it clarify when each sub-operation (list vs. get vs. map) is appropriate. No exclusions or alternative references are given.

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