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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral context beyond them: ordering (newest first), the meaning of each status, and the important non-obvious fact that 'superseded' and 'discarded' versions are kept in history and can be re-promoted. It also flags ordering as fixed. Missing only pagination/response-shape behavior, which is defensible given no output schema.

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?

Front-loaded with the core statement, then the status vocabulary delivered as a scannable definition list. It is long, but with no output schema the field/status enumeration earns its space; the trailing '$0' is a slightly cryptic appendage.

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 correctly carries the return-field burden and explains the domain-specific status vocabulary thoroughly. Gaps remain around the required project_id and pagination behavior across the limit, but the semantic coverage is strong for a list tool.

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 coverage is only 50%: 'limit' is documented in the schema but 'project_id' has no description anywhere. The description enumerates return fields (id, number, sequence, parent, origin...) rather than explaining the inputs, so it does not compensate for the undocumented required parameter.

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+resource ('The project's version timeline ... with lineage') and enumerates exactly what is returned. In a sibling set crowded with list_* tools (list_projects, list_ops, list_cast, list_material, list_referents), it unambiguously stakes out the version/lineage domain.

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?

No statement of when to call this versus siblings like get_project_status, set_head, or get_project_vbp — all of which touch the same version/cut concept. The 'isHead' and status semantics imply a use case (finding the current cut), but the agent must infer it; 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.