get_my_project_access

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It clarifies this is a read-style operation and that the result is the current user's own membership with 'inferred' access hints, adding some context, but it does not explain the meaning of 'inferred access hints' or any limitations/error semantics.

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, front-loaded sentence with no filler. Every word contributes to understanding the tool's core function.

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?

The tool is simple with one parameter and an output schema, so the description need not explain return structure. However, it is incomplete for a tool with no annotations: it lacks guidance on when to use it, what 'inferred access hints' means, and how the project parameter should be supplied, leaving the agent to guess these important aspects.

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 'project' has zero schema description coverage and the description does not add any meaning beyond the schema's title. The tool description mentions 'for a project' but provides no guidance on ID format, project reference type, or required context, failing to compensate for the low schema coverage.

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 tool returns the current user's membership and inferred access hints for a specified project, using a specific verb ('Return') and a specific resource. It differentiates itself from siblings like list_project_memberships and get_current_user by focusing on the current user's project-specific access context.

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 implies usage when needing the current user's project access/membership information, but it provides no explicit guidance on when to use this over alternatives like get_membership or list_project_memberships, nor does it mention exclusions or preferred contexts.

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