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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds the GET endpoint and the filterable dimensions but says nothing about pagination behavior, result caps, or what 'projects' contain beyond being groups of jobs. Useful but modest added context.

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?

Two short sentences, front-loaded with the action and resource, with the disambiguating parenthetical placed where it matters. No filler.

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 an 11-parameter, zero-required read tool with no output schema, the definition covers the verb, the object, and the filter axes but omits pagination guidance and any hint of the returned record shape. Adequate to invoke, not complete for a broad list endpoint.

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 only 27%, so the description must compensate, and it does partially by naming the four filter dimensions (customer, site, equipment, project type) that map to customer_id/equipment_id/site_id/type_id. It does not explain the _id vs _my_id parameter pairs, type_name vs type_id, or the zero-required-parameter nature, leaving several undocumented parameters unresolved.

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?

States a specific verb and resource ('List projects') and immediately disambiguates the domain object as 'groups of jobs,' which distinguishes it from the sibling synchroteam_list_jobs. It also gives the underlying endpoint. It stops short of naming siblings explicitly, so it is clear but not maximally differentiated.

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?

Listing the filter dimensions (customer, site, equipment, project type) implies when this tool is appropriate, but there is no explicit when-to-use versus list_jobs guidance and no note that all filters are optional. Usage is inferable rather than stated.

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