provider_get_current_session_rights

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), so the description's real contribution is the caveat that 'impliedRights' and 'isPublishable' will not be populated — a genuinely useful disclosure that prevents an agent from misreading missing fields as an error. It adds no pagination or rate-limit behavior, which keeps it from a 5.

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 repeats the core sentence verbatim ('Returns the rights associated with the current session' appears twice), which is pure waste. What remains — the field caveat and the endpoint path — is front-loaded and useful.

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?

No output schema exists, so the description carries return-value burden; it partially addresses this with the missing-field caveat but never describes the overall shape of a right object or pagination response. Adequate minimum for a read-only list endpoint, but not complete.

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 coverage is 100% with documented page, pageSize, filter (FIQL), and sort fields, so the schema does the heavy lifting. The description says nothing about filtering, sorting, or pagination semantics, giving no value beyond the schema.

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 and resource with scope: 'Returns the rights associated with the current session.' The 'current session' qualifier implicitly separates it from broader siblings such as provider_query_rights or provider_get_right, though it never names them explicitly.

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 guidance on when to use this versus provider_get_current_session, provider_query_rights, or provider_get_right. The usage is inferable from the name only; no prerequisites, exclusions, or alternatives are stated.

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