hub_process

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows it may mutate but is not destructive; the description does not contradict this. However, it says nothing about the six distinct actions (propose vs update vs list vs report), whether proposals require approval, or what gets overwritten on update — meaningful behavioral gaps the annotations cannot cover.

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 wasted words, and the resource definition is front-loaded. The brevity is not padding, though it edges toward under-specification rather than crispness.

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?

This is a multi-mode tool with a six-value action enum, a nested 'note' object, and no output schema, yet the description explains none of the modes, the note structure, or the return shape. For that complexity, two sentence fragments leave an agent unable to call it correctly without guessing at the enum semantics.

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%, so the baseline is 3 even though the description adds no parameter detail. This is generous here because the schema's own text is cryptic ('What to do.', 'when, steps, commands, pitfalls, areas, scope.'), but the rule assigns the schema the burden at full coverage.

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 names a resource ('process notes: how the crew does things') but no verb beyond the vague 'Record yours', so it never says whether this creates, retrieves, or lists. It is essentially a restatement of the tool name 'hub_process' and gives no basis for distinguishing it from siblings like hub_file or hub_history.

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?

'Record yours' weakly implies you should use it when you have a process to document, but there is no when-to-use guidance, no prerequisites, and no mention of alternatives among the 13 sibling tools. Nothing tells an agent when to pick this over hub_file or hub_task.

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