provider_query_rights

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds useful scope context ('visible to logged-in user') and the underlying endpoint, but does not describe pagination behavior, filter semantics, or what the returned rights look like.

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 short and front-loads the core purpose, but it repeats the same idea twice ('Get list of rights visible to logged-in user' followed by 'Get list of rights') and then appends the raw endpoint. Each line is not maximally earning its place.

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?

This is a simple read-only list endpoint with full schema coverage and annotations that communicate safety. The description states the visibility scope, and the schema covers paging, filtering, and sorting. A brief note on returned rights format would help, but the essential context is present.

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 100%, so all five parameters including page, pageSize, filter, sortAsc, and sortDesc are already documented in the schema. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 3 applies.

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 first sentence names a specific verb ('Get') and resource ('list of rights') and adds the scope 'visible to logged-in user'. It is clear what the tool returns, though it does not explicitly distinguish itself from siblings like provider_get_right or provider_get_current_session_rights.

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?

The description gives no when-to-use guidance or alternatives. It does not explain why an agent should call this instead of provider_get_current_session_rights, provider_query_role_rights, or provider_get_right, leaving selection entirely to inference.

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