get_lifecycle_gaps

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds that it returns timestamps, identities, and missing-parent evidence, which is useful, but it does not explain behavior such as whether the limit parameter controls pagination or if the tool operates only on certain artifact types.

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 description is extremely concise at just seven words, and every word is functional. However, the brevity sacrifices necessary context and definition, making it cryptic rather than efficiently clear.

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 an output schema present, the return structure is known, but the description does not explain what 'lifecycle gaps' are or when this tool should be used. It lacks the context needed to understand the tool's role among the many sibling tools, making the description incomplete.

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 schema has two parameters (artifact_id and limit) with 0% description coverage. The tool description does not mention either parameter, so the agent gains no semantic understanding of how to fill them. The description fails to compensate for the schema's lack of detail.

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 specifies that the tool returns 'explicit timestamp, identity, and missing-parent evidence,' which indicates a clear output type but leaves the core concept of 'lifecycle gaps' undefined. It does not differentiate itself from sibling tools like get_evidence or extract_* tools, making the purpose only vaguely clear.

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 description provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent without information about appropriate invocation scenarios.

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