aiworkhub_session_token_profile

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

readOnlyHint=true is already declared, and the description reinforces it with the 'READ-ONLY' prefix. It adds one genuine piece of behavioral context by clarifying that prompt bytes are labelled separately from observed provider tokens, which hints at data provenance. It does not state the scope (per session? per task?), whether results are cached, or freshness, so the added value is moderate.

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 short sentence with the safety qualifier front-loaded, so nothing is wasted. It is slightly terse to the point of being cryptic — 'separately-labelled prompt bytes' requires interpretation — but it is well sized for a one-parameter read tool.

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?

An output schema exists, so return values need no explanation, and the annotation covers safety. But the description omits the scope of the profile (session-level vs task-level) and leaves the only parameter undocumented, gaps that neither the schema nor the annotations fill.

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 single parameter task_id has 0% schema description coverage, and the description never mentions it. With only one optional parameter and no documentation anywhere, the agent has to infer that omitting it yields a global/default profile and supplying it narrows to one task.

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 names the resource semantically (session token profile) and describes its contents: observed provider tokens plus prompt-byte counts reported separately. However, there is no explicit verb and no differentiation from closely related siblings such as aiworkhub_task_usage_report or aiworkhub_task_cost_ledger, so an agent cannot tell from the text alone which one to pick.

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?

There is no when-to-use statement, no prerequisites, and no mention of alternatives. The description states what data exists but never says under what circumstances an agent should call this rather than the usage report or cost ledger tools listed as siblings.

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