User: Get_user_suspended_status

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The phrase 'Check whether' weakly implies a boolean-style answer, but the description adds nothing about rate limits, permissions, or what a non-suspended versus unknown user looks 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?

A single well-formed sentence with zero filler and the action front-loaded. It is appropriately sized for a one-parameter read tool, though it is lean enough that it borders on under-specification.

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?

For a simple read-only lookup with one fully documented parameter and no output schema, the description covers the essentials but leaves the response shape unspecified — the agent cannot tell whether it receives a boolean, a status string, or a full user object.

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 userId parameter has 100% schema description coverage ('The Brivo user id.'), so the schema carries the load and a 3 is the appropriate baseline. The description adds no extra meaning about id format or accepted sources (e.g., external id vs. internal id).

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 ('Check') and a precise attribute of the resource ('whether a user is suspended'), so the agent knows exactly what the call answers. It doesn't distinguish itself from siblings such as Get_user, which plausibly also exposes suspension state, so a 5 is not warranted.

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 guidance, no prerequisites, and no mention of alternatives like Get_user or List_users that might already return suspension information. Usage must be inferred entirely from the name and one-line description.

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