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

The only behavioral statement, 'Side effects: none (read-only)', merely restates the readOnlyHint annotation and does not add context such as error behavior, authorization requirements, or rate limits. The description is not contradictory, but it contributes no behavioral information beyond what the annotations already encode.

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 purpose is front-loaded in the first sentence and the side-effect note is a separate short line. There is no filler, making the description appropriately sized for a one-parameter tool.

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 lookup, the description, full parameter schema, output schema, and annotations together give an agent enough to call the tool correctly. The only missing piece is guidance on when to choose this tool over sibling member/user tools.

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 parameter member_user_id is already described in the input schema with 100% coverage, so the description does not need to add much. The mention of 'corporate member' hints at the expected resource type but does not add syntax or constraints beyond the schema.

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 names a specific resource and outcome: it retrieves a corporate member's role and faxing quota. This is clearer than the generic title, but it does not explicitly differentiate this tool from siblings like get-user or list-members.

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 usage context is provided: the description does not say when to prefer this tool over get-user or list-members, nor does it mention prerequisites such as needing a corporate member ID. With over thirty sibling tools, the agent must infer routing from the name alone.

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