group_current_page

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does convey the core trait — this is a non-destructive read operation that 'returns' the current page. However, it does not disclose the return format (number vs. label, 0-based vs. 1-based) or behavior when the referenced element is not a page-group, leaving meaningful gaps.

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?

The description is a single front-loaded sentence with no filler; the verb and resource appear immediately. It is appropriately brief for a simple getter, though the brevity is part of what allows parameter semantics and context to go unaddressed.

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?

The tool has three undocumented parameters (all optional, with defaults), no output schema, and no annotations, yet the description explains neither how to identify the target form element nor what the tool returns. An agent cannot reliably invoke this tool correctly based on the definition alone.

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 description mentions none of the three parameters (name, title, session_id), so it adds no meaning beyond the bare schema. The agent is left to guess which parameter identifies the form element or whether session_id scopes the lookup, and nothing compensates for the coverage gap.

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?

The description states a specific verb ('Return') and a specific resource ('current page of a page-group form element'), which clearly identifies it as a read-only getter. This distinguishes it from siblings like group_activate_page (which changes pages) and group_expand/group_collapse (which alter visual state), so an agent can tell it apart without opening schemas.

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 is given on when to use this tool versus alternatives such as group_state or group_activate_page. There is no mention of when not to use it, no stated preconditions (e.g., the group must be a page-group), and no routing to sibling tools.

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