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

With no annotations, the description carries the disclosure burden. It reveals that results are publicly published profiles and that no account is needed, and 'search' and 'browse' imply read-only behavior. It does not disclose result shape, pagination, or rate-limit behavior, but for a simple search this is acceptable.

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?

Two tight sentences front-load the tool's purpose and use cases without padding. Every clause contributes useful information, and the structure is easy to scan.

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 low-complexity tool with two optional parameters and no output schema, the description covers purpose, access requirements, and use cases well. It could more explicitly describe what fields a returned role profile contains, but the phrase 'role profiles' plus search-by-title is enough for correct invocation.

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 only 50%: query is described in the schema, and the description does not add meaning for the limit parameter. The limit field is simple enough to infer from its type, default, min, and max, but the description itself adds no parameter-level guidance.

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 opens with a concrete verb and resource: 'Search the public WorkforceGPT role library'. It also clarifies this is a lookup of author-published profiles and explicitly notes it requires no account, separating it from account-scoped siblings like list_my_roles get_role, or get_public_role.

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 concrete reasons to use the tool: finding examples of generated profiles or prior art on a title. 'Needs no account' tells an agent it is the right choice in no-authentication contexts, though it does not explicitly name alternatives or exclusions.

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