yougile_get_project_role

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds nothing beyond the obvious read operation. It does not mention any additional behavioral traits like permissions, pagination, or return format, so it provides minimal value beyond the annotations.

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 a single, clear sentence with no fluff. It is concise, though it could be slightly enhanced with a usage note or scope constraint, but it is appropriately sized for a simple getter 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 simple get-by-ID tool with full parameter schema and read-only annotations, the description is adequate but slightly incomplete. It does not mention the absence of output schema or specify response behavior, and it lacks contextual guidance about when to prefer this over listing roles. Overall, it covers the minimum but leaves room for clarity.

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 100% with both roleId and projectId described as UUIDs. The description itself adds no parameter details beyond what the schema already provides, so it meets the baseline for schema-covered params.

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 verb 'Get' and the resource 'a specific role in a project', which accurately distinguishes this tool from siblings like yougile_list_project_roles (list all) and yougile_create_project_role/update/delete. It precisely indicates a single-entity retrieval operation.

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 does not explicitly state when to use this tool versus alternatives, such as yougile_list_project_roles. The usage is implied from the words 'specific role', suggesting one should already have the roleId and projectId, but no explicit guidance or exclusions are provided.

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