get_my_project_collection

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds the meaningful scoping fact that results are limited to the caller's memberships, but says nothing about default page size, result caps, or authentication requirements.

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 opening two sentences say nearly the same thing ('Get all assigned projects' / 'Retrieve all projects that the authenticated user is a member of'), which is redundant. The remaining guidance is brief and front-loaded, so the overall shape is fine but not tight.

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?

With no output schema, the description should carry more of the return-shape burden, and with a complex nested filter/relations schema it should offer more than a one-line pointer to relations. It covers the broad capabilities adequately but leaves pagination defaults, sorting syntax, and result envelope unstated.

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?

Top-level schema description coverage is 0% and the single 'query' parameter is a large nested object. The description names the capability buckets (filters, sorting, pagination, relations) which maps onto the schema's groups, but adds no syntax, defaults, or field-level meaning beyond what the nested field descriptions already provide.

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?

It states a specific verb+resource and a clear scope: projects the authenticated user is a member of. That distinguishes it conceptually from the sibling get_project_collection, but the description never names that sibling, so the agent must infer the boundary from the tool name alone.

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?

Usage is implied ('Apply custom filters, sorting, and pagination') rather than instructed. There is no statement of when to prefer this over get_project_collection or get_project, and no prerequisites or exclusions are given.

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