Get company user directory

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

Description adds the HTTP method (GET) and authorization class, which supplements annotations (readOnlyHint, destructiveHint). However, it does not disclose behavior like pagination or error handling. Annotations already cover safety profile.

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?

Very short (two sentences), but the first sentence is redundant with the title. No wasted words, but also lacking substance. Could be improved with parameter details.

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?

Given the simplicity (1 parameter), the description is incomplete. It does not explain the output or how to use it, though an output schema exists. The tool's purpose remains vague.

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?

With 0% schema description coverage, the description must explain the parameter 'companyId' but fails to do so. The parameter is entirely undocumented, leaving the agent without 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 clearly states 'Get company user directory', which specifies the action (get) and resource (user directory). It distinguishes from sibling tools like pc_get_companies by specifying the directory, but lacks detail on what the directory contains.

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?

No guidance on when to use this tool versus alternatives. No context about prerequisites, exclusions, or typical use cases.

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