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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety profile needs no restating. The description adds the paged nature of the response and the next_page continuation mechanism, which is genuinely useful behavioral context, but says nothing about result shape, default limit behavior, or empty results.

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 fragments with no waste, and the scoped subject is front-loaded ahead of the pagination note. Slightly telegraphic phrasing ('Paged: use next_page') costs it the top mark.

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 full schema coverage, one required id, and annotations covering the safety profile, the description supplies what an agent needs to call it and page through results. The lack of any indication of what a returned project contains is a minor gap since no output schema exists.

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% and every parameter (page, limit, geofence_id, is_archived) is documented inline, so the baseline of 3 applies. The description's only added semantics is the paging hint, which the schema already covers.

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 the specific resource (projects) and the exact scope (attached to one geofence/work site), so an agent can distinguish it from workyard_list_projects and workyard_list_geofences. It falls short of 5 only because it doesn't explicitly name the alternative tools it is not.

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 phrase 'Paged: use next_page' gives concrete pagination guidance, and the required geofence_id implies usage after workyard_list_geofences. However, there is no explicit when-to-use/when-not statement or named alternative, so the guidance is implied rather than stated.

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