get_session

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the request bound (one call to Odoo.sh, zero when no session exists), which tells the agent about cost and side-effect-free fallback behavior.

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?

Nicely front-loaded with labelled sections (Returns/Touches/Bounds) and each line is short. There is mild redundancy: the opening sentence's 'where it came from and who it belongs to' is restated as 'its source, its user' in the Returns line.

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 enumerating return fields is optional padding rather than required content. With annotations carrying the safety profile and the bounds line carrying the operational cost, the only real gap is the absence of guidance on when this check should be invoked relative to the sibling tools.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter claims are made or needed.

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?

States a specific verb (Report) and resource (Odoo.sh session) with the exact fields surfaced: availability, source, user, and seconds until max age. This is clearly separable from the build/branch/project/log siblings, none of which touch session state.

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?

Usage is only implied — an agent can infer this is a diagnostic/authentication-state check to run before other Odoo.sh operations. There is no explicit when-to-use, no prerequisite statement, and no named alternative or condition for skipping it.

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