mogut_discover_profiles

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

With no annotations provided, the description carries the behavioral burden. 'Lists' signals a read-only action and the sentence specifies returned content, but it does not disclose possible limitations, failure modes, how 'loaded' is represented, or whether any state changes happen. This is adequate, not rich.

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 with zero filler. It leads with the action and immediately describes the meaningful parts of the result. Every part of the description earns its place.

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 zero-parameter tool with no output schema, this description gives enough orientation: it says what the operation produces and at what scope. It could add detail like the exact return format, but nothing critical is missing for an agent deciding whether to invoke it.

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?

The tool has zero parameters and the input schema is empty, so there is little parameter-level semantics to add. The description appropriately focuses outward on what is returned rather than on inputs.

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?

Uses a specific verb ('Lists') and resource ('every profile'), and describes exactly what the output contains: load status and tools. This cleanly separates it from sibling tools like mogut_discover_sources and mogut_search_tools, which focus on different resources.

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 description implies when to use it: when the agent needs a full inventory of profiles and their loaded-state/tools. However, it never explicitly names an alternative or explains when not to use it, leaving the routing decision to inference based on sibling tool names.

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