get_project_collection

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds that filters, sorting, pagination, and relations are supported, but does not disclose pagination defaults, rate limits, or response format.

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 first two sentences are redundant ('Get all projects. Retrieve all projects.'), which hurts conciseness. The remaining sentences are front-loaded and informative, but the repetition is unnecessary.

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 tool has a complex nested filter object and no output schema. The description covers high-level capabilities but omits details like pagination limits, default page size, and the exact parameter names for relations and filters, leaving some gaps for an agent to fill from the schema.

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 description refers to a 'relations parameter,' but the schema uses 'with' inside the 'query' object. It does not explain the nested structure or provide syntax details, and top-level schema description coverage is 0%, so the description fails to fully compensate for the gap.

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: 'Get all projects' / 'Retrieve all projects.' It distinguishes itself from the singular get_project tool implicitly, but does not explicitly differentiate from sibling collection tools like get_my_project_collection.

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?

It mentions applying custom filters, sorting, and pagination, which implies usage, but provides no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

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