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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered and the description need not restate it. The description adds the underlying endpoint (GET /users/chefs) and the returned field set, but says nothing about pagination behavior, volume, or what an empty result means for a non-Chef-ID account.

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 sentences with the field list front-loaded and the precondition immediately after; nothing is padded. The trailing "GET /users/chefs" is a small implementation detail but costs little.

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 enumeration of returned fields (id, email, join date, active flag, permission level, chef tag) fills the biggest gap an agent would otherwise have. Pagination is documented in the schema rather than the description, so the only real omission is what a caller should do when the account lacks Chef IDs.

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 all three parameters (limit, offset, search) are fully documented in the schema, including the next_offset handoff, so the description rightly does not repeat them. It adds no semantics beyond the schema, which is the baseline case.

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 and resource ("List the chef users of the account") and enumerates the returned fields, so the agent knows exactly what data comes back. It never names a sibling, so the agent must infer that parsley_list_chef_tags covers tags rather than users, but the name and field list make the scope unambiguous.

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?

"Only meaningful for accounts with Chef IDs enabled" is a genuine precondition that tells the agent when this tool is worthless, which is more than most list tools offer. It stops short of naming alternatives (e.g. parsley_list_chef_tags) or saying how to detect whether Chef IDs are enabled, so it is clear context rather than full routing guidance.

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