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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds modest value by disclosing the returned entities and explaining that project_version is 'the version every scene call carries' — useful domain context, but no notes on auth, size or pagination.

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?

A single sentence, so nothing is padded, but the trailing 'Arguments: {...}' restates the schema verbatim and dilutes the otherwise dense field list. Front-loading is fine; the redundant schema echo costs it.

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 enumerates what is returned, which is the main thing an agent needs. However it omits any usage context or guidance against sibling getters, so it is adequate rather than complete.

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 0% and the parameter is a nested object, so the description must carry the meaning. It does clarify that the nested id is a '<project id>' and even shows the literal argument shape, but that largely mirrors the schema rather than adding syntax, format or constraint 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?

It names the resource (a project) and enumerates exactly what is read: scene brief, selected files, preparation state, jobs, messages, project_version. But the leading frame 'Read a conversation' is an odd/misleading label for a get_project tool, and nothing distinguishes it from siblings like kelpo_get_editing, kelpo_get_job or kelpo_get_shoot.

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 the many other get_*/list_* siblings, and no prerequisites or context. The agent is left to infer that this is the project-root read.

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