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

Annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds the returned project fields and mentions that it is a GraphQL query, but it does not add further behavioral context such as pagination behavior, authorization requirements, or rate limits.

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 short and front-loads the purpose and returned fields. The second sentence, 'GraphQL query projects,' is largely an implementation detail and does not contribute much, but the overall definition remains efficient.

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 simple read-only list tool with no output schema, the description provides the essential returned fields and the schema covers pagination and sorting details. It is adequate, though it could mention pagination or the single-project alternative more explicitly.

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 80%, so the schema already documents most parameters and provides the baseline of 3. The description mentions the status values ACTIVE or INACTIVE, but this duplicates the enum already present in the schema and does not add meaning beyond it.

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 specific verb and resource: 'List time-tracking projects'. It also names the returned fields (id, name, status) and distinguishes itself implicitly from the singular get_project sibling. It stops short of explicitly differentiating from other project-related siblings like get_project or create_project.

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 says what the tool lists but provides no when-to-use guidance, exclusions, or alternatives. It does not tell the agent when to list projects versus retrieving a single project with get_project, nor does it explain when status filtering or pagination should be used.

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