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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not explicitly state that the operation is read-only or non-destructive, nor does it mention authentication requirements, pagination behavior, or any side effects. The phrase 'List your projects' implies a read operation but does not confirm it, leaving the agent to infer safety.

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 sentence with no unnecessary words. It is front-loaded with the core purpose. While extremely brief, it avoids redundancy and is structurally efficient. However, it is so terse that it verges on under-specification, preventing a perfect score.

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?

The description is minimal but the output schema exists, so return structure is covered. However, it does not mention filtering, pagination, or ownership scoping, which are part of the tool's behavior. The agent must rely on the schema to understand these capabilities. For a list tool with five parameters, the description is adequate but lacks enrichment that would help an agent understand when to use it in different scenarios.

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 all five parameters are already documented with descriptions. The tool description adds no additional meaning about the parameters. Per the rubric, a baseline of 3 is appropriate when the schema fully covers parameter semantics.

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 states a clear verb and resource: 'List your projects.' This is unambiguous and distinguishes from sibling tools like get_project (singular) and list_project_resources (which lists resources within a project). However, it does not explicitly differentiate itself from other list operations, so it misses the top score.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of when list_projects is appropriate compared to get_project, list_project_resources, or other list operations. It simply states what it does without context on selection criteria.

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