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

No annotations are provided, so the description carries the full burden. It discloses the admin requirement and the output fields (profile_id, email, roles, providers, ban status). However, it lacks details on pagination, limit behavior, and exact matching semantics of q/role, and the 'or' in 'filter by q or role' is ambiguous.

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 two sentences, front-loaded with the action, and every clause adds value. It avoids repetition of schema content and is efficient for an agent to parse.

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 list tool with no output schema and no annotations, the description covers the essential aspects: purpose, filters, and output fields. It omits pagination and limit defaults, but these are minor for a read-only listing tool. Overall, it is sufficiently 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 description coverage is 0%, so the description must compensate. It explains q as 'name/email/orcid' and role as a filter, adding value beyond the schema. However, it fails to mention the limit parameter, which is only self-evident from its name and default in the schema. Partial compensation leaves a gap.

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 clearly states the action: 'List users (profiles)' with a specific resource and context. It distinguishes from sibling list tools by naming the object type and specifying filter options (q, role), making its purpose unambiguous.

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 '(Admin)' prefix indicates restricted usage context. The description implies when to use it (admin user listing with filters) but does not explicitly name alternatives or provide when-not-to-use guidance. The context is clear enough for an agent to select it among sibling list tools.

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