can_read

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

The annotations already indicate readOnlyHint: true and destructiveHint: false, and the description is consistent with these (no side effects mentioned). However, the description adds no extra behavioral context beyond what the annotations provide, such as whether the check counts against any quotas or triggers logging.

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 extremely concise and to the point, with no unnecessary verbiage. It conveys the essential information in one sentence, making it easy for an agent to parse quickly.

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 description does not mention the return value or output format. Given that an output schema exists (though not shown here), an agent might infer the result is a boolean, but this is not explicitly stated. For a simple permission check, this is a minor gap, but it would be improved by noting the expected response (e.g., 'returns true if access is granted').

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 description provides useful context for workspace_id (pointing to list_workspaces) and target_type (listing possible values), but leaves target_id entirely unexplained. Since schema descriptions are absent (0% coverage), the partial explanation is somewhat helpful but incomplete, especially for the target_id parameter.

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 ('Check'), the resource ('read access to a target'), and the scope ('current user'). It is unambiguous and directly distinguishes this tool from sibling permission checks like can_edit or can_archive.

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 is given for when to use this tool versus alternatives. While the purpose is clear, the description does not mention any conditions, exclusions, or comparisons with similar permission-check functions, leaving the agent to infer appropriate usage 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.