fmod_window_browserCurrent

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

With no annotations, the description must disclose behaviors. It mentions returning a ManagedObject and optional tabName, but fails to describe error handling, side effects (none), or what happens if no selection exists. The repetitive text adds no value.

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, but the first sentence is repeated verbatim, wasting space. The bracketed technical suffix is unnecessary verbosity. Could be more concise.

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?

Given no output schema, the description should clarify what the returned ManagedObject is (e.g., its type or structure). It doesn't describe error conditions or edge cases. For a simple retrieval tool with one optional param, it is incomplete.

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 has 1 parameter (tabName) with minimal description '(optional)'. The description adds that it selects from a different browser tab, providing context. However, schema coverage is 100% but schema description is poor, so description slightly compensates.

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?

Description clearly states it returns the currently selected ManagedObject in the active browser tab of the last active window, with optional tabName. It is specific and not a tautology, though it doesn't differentiate from siblings like fmod_window_browserSelection.

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 guidance on when to use this tool vs alternatives. The description only mentions an optional parameter but no conditions or exclusions. Among many sibling tools, the agent lacks context for selection.

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