grokbot_list_secrets

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

readOnlyHint already declares this as a non-mutating read, so the bar is lowered, yet the description still adds the genuinely useful fact that secret values are never returned. It leaves out whether descriptions can be truncated or what permissions are needed, but the key security behavior is disclosed.

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 sentences with no filler, and the security-relevant constraint (values are never returned) is placed prominently right after the purpose.

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?

For a simple read-only list with an annotation covering safety and no output schema, the description provides enough to call it correctly. Only minor gaps remain, such as permissions or result ordering/count.

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 single parameter agent_id is undocumented in the schema, so the description carries the burden. It does not explain the parameter at all, but the name is largely self-explanatory for an agent-scoped list, keeping this at the minimum-viable level.

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?

Specific verb (List) plus resource (secret names and descriptions) scoped to an agent. It clearly separates itself from grokbot_put_secret and grokbot_delete_secret by being the read/list counterpart, though it never names those siblings explicitly.

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 when-to-use guidance, no prerequisites, and no mention of alternatives like grokbot_put_secret or grokbot_delete_secret. The intent is inferable from the verb but nothing is stated.

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