mimicus_browse_categories

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the agent knows this operation writes/refreshes state in an open world. The description adds useful color consistent with that profile: fetching produces a "fresh" view (explaining the non-idempotent write) and normalized concepts are separately labeled. It does not contradict the annotations, but adds only modest context beyond them.

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 dual mode (explore vs. fresh view) is stated up front. The wording is dense with internal jargon, but nothing is padded or repetitive.

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 tool with two undocumented parameters, no required-parameter signal, and no usage guidance, the description is too thin. Output schema exists so return values need not be explained, but the agent still lacks the plain-language purpose and parameter meaning needed to invoke it correctly.

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%, so the description must carry the parameter burden. "source-native" and "active operation" only obliquely gesture at the provider enum and operationId; neither parameter is named, explained, or given format expectations, leaving both effectively undocumented.

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?

"Explore source-native taxonomy" is essentially a jargon paraphrase of the name browse_categories, and "fetch a fresh bounded source view" is equally opaque. No concrete noun like "categories/tags for a source" is used, so an agent cannot quickly confirm the resource being enumerated, and no sibling (e.g. mimicus_list_sources, mimicus_search) is distinguished.

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 phrase "in an active operation, or fetch a fresh bounded source view" gestures at two modes but never states the condition that selects one over the other, nor when this tool should be used instead of mimicus_list_sources or mimicus_search. It is implied context at best, with no exclusions or prerequisites.

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