get_project_user

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description adds no behavioral context beyond the endpoint — no mention of permissions required, error behavior for non-members, or response shape.

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 short fragments with zero filler, and the endpoint is front-loaded as the second sentence. However, the brevity is under-specification rather than disciplined conciseness — the 'Get Users' fragment earns nothing.

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 two-parameter read tool with full annotation coverage, the minimum is met, but among ~150 siblings the description gives no disambiguation and no return-value hint (no output schema exists). An agent could easily pick the wrong user-fetching tool.

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 0%, so the description carries the burden; the path template does indicate that project_id scopes to a project and user_id identifies a user within it, which is real added meaning. It still omits that these are integer IDs and omits any constraint or format detail.

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 REST path 'GET /project/{project_id}/users/{user_id}' does pin down that this retrieves a single project-scoped user, but the prose 'Get Users' is plural and tautological. It never distinguishes this from siblings like get_user, list_users, or list_project_users.

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 statement of when to use this instead of list_project_users (list) or get_user (global lookup). The agent must infer the single-resource-vs-list distinction purely from the endpoint string.

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